A fault policy bindings file associates the policies defined in a fault policy file with the SOA composite application or the component (service component or reference binding component). The framework attempts to identify a fault policy binding in the following order:

• Reference binding component defined in the composite.xml file.

• BPEL process or Oracle Mediator service component defined in the composite.xml file.

• SOA composite application defined in the composite.xml file.

During the resolution process, if no action is found that matches the condition, the framework assumes that resolution failed and moves to the next resolution level.

For example, assume an invoke activity faults with faultname="abc". There is a policy binding specified in the fault-bindings.xml file:

• SOA composite application binds to policy-id-1

• BPEL process or Oracle Mediator service component or reference binding component binds to policy-id-2

In the fault-bindings.xml file, the following bindings are also specified:

• SOA composite application binds to policy-id-3

• Reference binding component or service component binds to policy-id-4

The fault management framework behaves as follows:

• First match the resolve binding (in this case, policy-id-4).

• If the fault resolution fails, go to the next possible match (policy-id-2).

• If the fault resolution fails, go to the next possible match (policy-id-3).

• If the fault resolution fails, go to the next possible match (in this case, policy-id-1).

• If the fault resolution still fails, the fault is sent to the BPEL fault catch activity.