This content has been marked as final. Show 4 replies
Somewhat comparable is the following fault policy:
<faultPolicy version="2.0.1" id="SpecifyFaultPolicyName">
... specify action ...
... remainder ...
Basically, you don't define any specific conditions, meaning all faults that are caught by the fault policy framework fall into this condition.
Mind: the fault-policy framework catches faults in invocations of (external) services from BPEL, Mediator, etc. Internal BPEL faults such as errored assign activities are not caught.
Kind regards, Ronald
Thanks very much Ronald, I'll try it and mark the answer.
May be helpful for others, the above answer is correct. A sample snippet for <Conditions> tag in fault-policies.xml
<!-- This acts like CatchAll -->
Hi Ronald Van,
what do you mean by this statement .
Mind: the fault-policy framework catches faults in invocations of (external) services from BPEL, Mediator, etc. Internal BPEL faults such as errored assign activities are >not caught.Is it like faults generated while invoking only will go to faultpolicies ?
I want to generate a email in case of faults to notify the customer. faultpolicies is working good for remote and binding fault and i am generating mail using java. but in case of selection failure it is not referring to fault policies. So Is generating a email from catchall block is the only solution for this or is there any other way.The problem with catch all block is that the instance state will be completed and my monitoring is affected. I want to generate a email and the process should be in running state . Is there any way?
Please suggest .
Thanks in Advance