Java Reference
In-Depth Information
NOTE
There are a lot of attributes of a BPEL document that can be statically validated. The writers of the
specification took special care to indicate throughout the spec the process violations that can be de-
tected at design time or compile time. For example, any implementation should be able to statically
enforce that a partner link is correctly constructed. So any designer tool should be able to find the
predominant number of errors in your process before it gets to a runtime engine, which is great.
From the palette, click the Reply label and drag it into the sequence after the Receive. Click
the edit icon to edit the attributes of the
<reply>
activity and enter the name “ReplyToClient”.
In the selector, choose “CustomerProcessPartnerLink” because that represents the client-fa-
cing output that you're replying to. Near the Output Variable field, click the Create… button
to create a variable that will hold the contents of your reply.
Note that you are not specifying a Fault Response. Your web service does not declare any
checked exceptions, and you're choosing to ignore runtime exceptions. In the real world, this
wouldn't be a great idea, and you'd normally want to specify a Fault Response and do more
robust error handling. I am avoiding the topic now to focus on the bare bones of creating a
running process. But if you do this in the real world and anything goes wrong in your web
service code, a SOAP fault with precious little helpful information will be thrown all the way
back to your client.
As shown in
Figure 9-10
, accept the default name of
CustomerProcessEsbOperationOut
and click OK.
