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 164 | Next

Frank Jennings, David Salter

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

The
fault handlers within the BPEL process allow us to do a similar thing. BPEL runtime
will attempt to match a fault to a specific Catch handler. If that cannot be found then
a fault will be handled by the Catch All handler if it is present.
Handling Events
[ 192 ]
For a Catch handler, we need to specify the name of the fault we wish to catch within
the Catch properties window.
Pressing the Fault Name "..." button within the properties window causes a dialog to
be displayed similar to that shown below from which the fault type can be selected.
Event Handlers
A BPEL process is initiated by receiving a message from a client, for example a web
service client. If the process is a synchronous process, then the client will wait for
the BPEL process to complete. The process will execute without any further input
from the client. This is how a typical short-lived process will execute. For more
complex asynchronous processes, it often becomes necessary to send additional
data to the BPEL process so that it can continue processing. BPEL mandates that a
receive activity can only be used to initiate a process and cannot be used afterwards
within a process. In a situation where we wish to send additional data to a running
process, we must use the OnMessage event handler.


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