SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 162 | Next

Frank Jennings, David Salter

"Building SOA-Based Composite Applications Using NetBeans IDE 6"


Providing a full description of these standard BPEL faults is out of scope for this
book. We suggest that you consult the BPEL language specification for further
details. (http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.pdf).
Finally, after selecting a faultMessage to throw, we need to specify which variable
holds the information or message to return to the calling application. Pressing the
Fault Variable "..." button within the properties window displays a dialog similar to
that shown below, which shows all the variables currently defined within the BPEL
process. Select the appropriate variable from this list and press OK.
Handling Events
[ 190 ]
To recap, when throwing a fault we:
1. identify a situation where we want to throw the fault
2. define the message to be sent to the client along with the fault
3. define the fault that we want to send to the client
Now that we have thrown a fault within our BPEL process, we need to catch it and
handle it. In its simplest case, this could be done by returning the fault message
we've just generated to the client application. Alternatively, we can perform some
additional BPEL processing and try to manage the fault case.
To manage thrown faults within a BPEL process, we have two options:
1. Catch a specific fault and deal with it
2.


Pages:
150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174