Time for action – the fault and termination handlers
Open the BPEL process that was used in the Time for action – adding scopes section and follow the ensuing steps:
Initially, the
<invoke>activity looks like the following screenshot:
Click on the following icon of the
<scope>activity and create a fault handler with a<catch>construct:
The
<scope>activity looks as follows:
The remaining task is to define the error handling logic. It can be any logic as we explained in Chapter 6, Fault Handling and Signaling.
What just happened?
In this section, we discuss the inner structure of the <scope> activity. We discuss defining local variables, partner links, handlers, and so on.
We can specify <partnerLinks>, <messageExchanges>, <variables>, <correlationSets>, <faultHandlers>, <compensationHandler>, <terminationHandler>, and <eventHandlers> locally for the scope, as shown in the following code. All are optional.
<scope...
