A business PROCESS sometimes needs to signal a fault explicitly. THEREFORE, BPEL provides the activity, which has the following syntax:

BPEL does not require DEFINITION of fault names prior to their use in the activity. This flexible approach can be error-prone, because there is no compile-time checking of fault names. In the case of typos, misspelled faults will not be handled by the designated fault handler.

Faults can also have an associated variable that contains fault data. If such a variable is required, you have to SPECIFY it when throwing a fault, by using the optional faultVariable

A business process sometimes needs to signal a fault explicitly. Therefore, BPEL provides the activity, which has the following syntax:

BPEL does not require definition of fault names prior to their use in the activity. This flexible approach can be error-prone, because there is no compile-time checking of fault names. In the case of typos, misspelled faults will not be handled by the designated fault handler.

Faults can also have an associated variable that contains fault data. If such a variable is required, you have to specify it when throwing a fault, by using the optional faultVariable