Java Reference
In-Depth Information
A new folder named after your test will appear. It contains a new test case called input.xml.
This is not a JUnit test case, but rather a complete SOAP envelope representing a valid input
based on your WSDL file. Here is the generated SOAP message that matches the input re-
quired by your WSDL operation:
<soapenv:Envelope
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:com:soacookbook">
<soapenv:Body>
<urn:getCustomerFullName>
<customerID>?3?</customerID>
</urn:getCustomerFullName>
</soapenv:Body>
</soapenv:Envelope>
The SOAP message is created according to the WSDL, with question marks inserted in the
customerID
element as place holders to indicate that you should supply meaningful values
that will produce the expected result. So enter “888” as the
customerID
element value be-
cause that's Homer Simpson's customer ID as defined by the massively complex business lo-
gic in your web service.
Executing the test
Now that you have a SOAP message ready to pass to the customer process, you need to invoke
it. Right-click on the test case and choose Run. This will invoke the service using your gener-
ated SOAP message, and will write the response to the Output.xmlfile in the same test folder
along with the input.
Here are the contents of the Output.xmlfile as returned by the BPEL orchestration, through
the service:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<ns1:getCustomerFullNameResponse
