This recipe explains how to handle the faults thrown from a synchronous BPEL process. A BPEL process uses the
<throw> activity in case of exceptional situations. It gives the client feedback on what went wrong with the BPEL process processing. In a scenario where the client is expecting the response message and does not capture the faults thrown from the BPEL process, we can define the inline fault in the BPEL process reply activity.
We modified the synchronous BPEL process to throw an exception when the input parameter says
FAULT. With the
check_fault condition, we check if the input parameter contains the word
FAULT. The modified BPEL process is shown in the following screenshot: ...