When a fault occurs within a business process, the process may not COMPLETE successfully. (But it can complete successfully if the fault is handled within a scope, which enables you to divide a complex process into several PARTS; more on scopes later.) The business process can handle the fault through one or more fault handlers. Within a fault handler, the business process defines custom activities that should recover from the fault and possibly reverse the partial (unsuccessful) work of the activity where the fault has occurred.

The fault handlers are specified before the first activity of the BPEL process, after partner links and variables.

The overall structure is shown in the FOLLOWING code excerpt:

Within the fault handlers, you specify several activities where you indicate which fault you want to catch and handle. Within a fault handler, you must specify at least one or . The activity can be specified only once within a fault handler.

Usually you specify several activities where you will handle specific faults and use to handle all other faults. To specify which fault you would like to handle, you must specify at least one of the following:

• faultName, which specifies the name of the fault to handle
• faultVariable, which specifies the variable type used for fault data

The FLEXIBILITY of activities is high, and all the following variations are PERMISSIBLE:

Fault handlers in BPEL are similar to try/catch clauses in modern programming languages such as Java.

When a fault occurs within a business process, the process may not complete successfully. (But it can complete successfully if the fault is handled within a scope, which enables you to divide a complex process into several parts; more on scopes later.) The business process can handle the fault through one or more fault handlers. Within a fault handler, the business process defines custom activities that should recover from the fault and possibly reverse the partial (unsuccessful) work of the activity where the fault has occurred.

The fault handlers are specified before the first activity of the BPEL process, after partner links and variables.

The overall structure is shown in the following code excerpt:

Within the fault handlers, you specify several activities where you indicate which fault you want to catch and handle. Within a fault handler, you must specify at least one or . The activity can be specified only once within a fault handler.

Usually you specify several activities where you will handle specific faults and use to handle all other faults. To specify which fault you would like to handle, you must specify at least one of the following:

The flexibility of activities is high, and all the following variations are permissible:

Fault handlers in BPEL are similar to try/catch clauses in modern programming languages such as Java.