In the sample process
shown earlier in this chapter, there is only one Throw activity so it's not too difficult
to keep track of it. In a more complex business process however, you may have
several Throw activities and it's useful to be able to easily identify them.
??? ??? ???
Handling Events
[ 188 ]
Secondly, we need to specify the Fault Name. This is analogous to the class of an
exception in Java code. The Fault Name can be selected from all the defined faults in
the WSDL files of any partners used by the BPEL process. To select the Fault Name,
we need to press the "..." button within the properties window. Selecting this causes
the dialog shown below to be displayed. This dialog shows all the fault messages
that are defined within the partner's WSDL Files in a hierarchical approach together
with all the System Faults that can be thrown. To select a fault, select it in the tree
view and press the OK button.
In addition to the faults defined within the partner's WSDL Files, the following
BPEL System Faults can also be thrown as shown in the following table:
completionConditionFailure Thrown if the completion condition for a "forEach" activity
can never be true.
conflictingReceive Thrown when two or more inbound message activities are
enabled for the same partner link, port type and operation.
Pages:
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172