1
<?xml version="1.0" encoding="UTF-8"?>
2
<definitions name="goodRRFOperation" targetNamespace="http://j2ee.netbeans.org/wsdl/goodRRFOperation"
3
xmlns="http://schemas.xmlsoap.org/wsdl/"
4
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
5
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
6
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/goodRRFOperation" xmlns:plink="http://schemas.xmlsoap.org/ws/2004/03/partner-link/">
8
<message name="goodRRFOperationOperationRequest">
9
<part name="part1" type="xsd:string"/>
10
<part name="part2" type="xsd:long"/>
12
<message name="goodRRFOperationOperationReply">
13
<part name="part1" type="xsd:string"/>
14
<part name="part2" type="xsd:long"/>
16
<message name="goodRRFOperationOperationFault">
17
<part name="part3" type="xsd:float"/>
18
<part name="part4" type="xsd:string"/>
20
<portType name="goodRRFOperationPortType">
21
<operation name="goodRRFOperationOperation" parameterOrder="bogus silly part2">
22
<input name="input1" message="tns:goodRRFOperationOperationRequest"/>
23
<output name="output1" message="tns:goodRRFOperationOperationReply"/>
24
<fault name="fault1" message="tns:goodRRFOperationOperationFault"/>
27
<binding name="goodRRFOperationBinding" type="tns:goodRRFOperationPortType">
28
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
29
<operation name="goodRRFOperationOperation">
32
<soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/goodRRFOperation"/>
34
<output name="output1">
35
<soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/goodRRFOperation"/>
38
<soap:fault use="literal" name="fault1" namespace="http://j2ee.netbeans.org/wsdl/goodRRFOperation"/>
42
<service name="goodRRFOperationService">
43
<port name="goodRRFOperationPort" binding="tns:goodRRFOperationBinding">
44
<soap:address location="http://localhost:18181/goodRRFOperationService/goodRRFOperationPort"/>
47
<plink:partnerLinkType name="goodRRFOperationPartner">
48
<!-- partnerLinkType are automatically generated when a new portType is added. partnerLinkType are used by BPEL processes.
49
In a BPEL process, a partner link represents the interaction between the BPEL process and a partner service. Each partner link is associated with a partner link type.
50
A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.-->
51
<plink:role name="goodRRFOperationPortTypeRole" portType="tns:goodRRFOperationPortType"/>
52
</plink:partnerLinkType>