Java Reference
In-Depth Information
<binding name="CustomerProcessEsbBinding"
type="tns:CustomerProcessEsbPortType">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="CustomerProcessEsbOperation">
<soap:operation/>
<input name="input1">
<soap:body use="literal"/>
</input>
<output name="output1">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="CustomerProcessEsbService">
<port name="CustomerProcessEsbPort"
binding="tns:CustomerProcessEsbBinding">
<soap:address location="http://localhost:${HttpDefaultPort}/
CustomerProcessEsbService/CustomerProcessEsbPort"/>
</port>
</service>
<plnk:partnerLinkType name="CustomerProcessEsb">
<plnk:role name="CustomerProcessEsbPortTypeRole"
portType="tns:CustomerProcessEsbPortType"/>
</plnk:partnerLinkType>
</definitions>
So as you can see in the source that you just created with the wizard (as noted you're also free
to write it by hand), the
<message>
values match what you specified by selecting them from
the imported schema, which defines the namespace
urn:com:soacookbook
. The rest of the
WSDL is pretty straightforward, but check out
Using Web Service Partners
on BPEL partner
links if you want a clearer picture of their role in the process. This step in the wizard is shown
in
Figure 9-6
.
