Handling faults

Earlier in the chapter, we introduced the fault handlers (<catch> and <catchAll>), where to locate them, and how to configure them. Also, we introduced you to the <throw> activity which signals faults explicitly so that the correct fault handler can trigger its fault handling logic. We also talked about WSDL faults and the fact that the BPEL runtime implicitly signals such faults.

In this section, we discuss how to define the fault handling logic within the fault handler (such as <catch> and <catchAll>).

Defining fault handling logic within <catch> and <catchAll>

The fault handling logic can be defined using any structural activities (such as <sequence>, <flow>, and <scope>) and behavioral activities (such as <invoke>, <assign>, and <reply>) that are defined in the WS-BPEL 2.0 specification. So a <faultHandlers> tag might look like the following code:

<faultHandlers>
  <!-- First fault...