Java Reference
In-Depth Information
xmlns:tns="urn:com:soacookbook"
messageType="tns:getCustomerFullNameResponse"/>
<variable name="CustomerProcessEsbOperationOut"
xmlns:tns="http://soacookbook.com/wsdl/CustomerProcessEsb"
messageType="tns:CustomerProcessEsbOperationResponse"/>
//...
</variables>
//...
<invoke ... outputVariable="GetCustomerFullNameOut"/>
<assign name="Assign2">
<copy>
<from>$GetCustomerFullNameOut.parameters/customerFullName</from>
<to>$CustomerProcessEsbOperationOut.getCustomerFullNameResponseEsb/
customerFullName</to>
</copy>
</assign>
Just as with the first
<assign>
, you're copying data out of the response that the web service
returned (packaged in the variable called
GetCustomerFullNameOut
) and putting it into the
global process variable called
CustomerProcessEsbOperationOut
.
NOTE
You have to do these assignments because you are mapping between what your client sees and how
the service is exposed. With an orchestration, these aren't the same thing! The client never sees your
internal WSDL here, as it is not invoked directly, but through the process, which has a slightly differ-
ent WSDL interface. However, you know that in this case, they wrap the same data types.
Check the source code
You now have a completed BPEL process that you are ready to package.
Example 9-4
shows
the complete CustomerProcess.bpelfile.
NOTE
You can view the source code of your BPEL file by clicking the Source tab at the top of the designer.
Example9-4.CustomerProcess.bpel
<?xml version="1.0" encoding="UTF-8"?>
<process
name="CustomerProcess"
targetNamespace="http://soacookbook.com/bpel/CustomerProcess"
