Fault Paths
Fault paths enable you to specify tasks to perform when a fault is thrown.
To view the fault path for the currently selected mediation operation, use the Show Fault Direction button at the top of the mediation paths area of the mediation flow editor. There is one Catch Fault task for each target operation in the mediation flow, and one Catch Fault task for faults encountered while processing the mediation flow.
Each target operation in a mediation flow has a Catch Fault task that catches faults thrown by the target operation. The faults can be either explicitly defined faults in the target operation’s service description, or they can be unhandled exceptions encountered during processing (for example, a NullPointerException).
The default Catch Fault task for a target operation has sub-paths for each declared fault in the target operation and one sub-path each for a time out fault and any undeclared faults. You can place mediation tasks on each sub-path to perform any post-fault processing for each fault.
To specify the same processing for multiple faults, you can configure the Catch Fault task to have fewer sub-paths by unselecting the Catch and Handle field for the fault. When you eliminate one or more sub-paths, the Catch All sub-path is required, and it is automatically enabled. Any faults that do not have a defined sub-path are sent to the Catch All sub-path.