Java Reference
In-Depth Information
<xs:sequence>
<xs:element name="customerFullName" type="xs:string"
minOccurs="0"></xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
Later in the orchestration, you will need to map the variables that the web service expects
(which are defined in this schema) to global variables within the process to enable interaction
between the client and the orchestration.
Here is the SOAP message used to invoke this web method:
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header/>
<S:Body>
<ns2:getCustomerFullName xmlns:ns2="urn:com:soacookbook">
<customerID>888</customerID>
</ns2:getCustomerFullName>
</S:Body>
</S:Envelope>
And here is the corresponding SOAP response message:
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:getCustomerFullNameResponse
xmlns:ns2="urn:com:soacookbook">
<customerFullName>Homer Jay Simpson</customerFullName>
</ns2:getCustomerFullNameResponse>
</S:Body>
</S:Envelope>
Now that you have a WSDL defined, you're ready to create a new BPEL process project and
add your service to it.
Creating a new BPEL process project
Through the SOA pack, NetBeans 6.1 allows you to visually create, build, and deploy
BPEL processes. You can download it from http://download.netbeans.org/netbeans/6.1/final/ .
Choose the “All” bundle, which contains the SOA pack. If you already have NetBeans in-
stalled but don't have the SOA pack, you can install it from Tools→Plugins→Available Plu-
gins within the IDE. Choose the SOA and BPEL plug-ins.
Search WWH ::




Custom Search