Earlier in the chapter, we categorized the possible types of errors that could be generated. One category of errors can be generated by the BPEL runtime itself. And those errors can be divided again into two subcategories based on whether the faults are signaled implicitly by the BPEL runtime or explicitly by the BPEL process developer. In order to explicitly signal faults by the BPEL process developer, we use the <throw> activity. The activity is explained in the Modeling logical (explicit) errors with <throw> activity section. But in this section, we demonstrate how to use the <throw> activity more thoroughly.

Also, we discussed faults that could be signaled by BPEL runtime implicitly due to the issues in the external environment such as WSDL faults.

These implicitly or explicitly generated faults either should be handled within the BPEL process or they should be propagated to an external party who can manage those faults. In the Handling...