Termination handler
When a BPEL process instance is executing, there are several scenarios which require that the currently executed activity of a process is terminated, for example:
When a fault handler is invoked, it disables the scope's event handlers and implicitly terminates all enclosed activities.
A fault in the fault handler causes the termination of all running contained activities.
When the
<completionCondition>is fulfilled for a parallel<forEach>activity, all still running directly enclosed<scope>activities are terminated.
This is called forced termination. Termination handler provides the ability for scopes to control the forced termination. The syntax of a termination handler is listed as follows:
<terminationHandler> activity </terminationHandler>
In a termination handler we can use the same range of activities as in a fault handler. We can use the<compensateScope> or<compensate> activities. However, in a termination handler we cannot...
