- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 536.4K On-Premises Infrastructure
- 138.3K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
BPEL Fault Handling
Today, i found something strange w.r.t Synchronous BPEL2.0.
I have 2 operations(First, Second) inside a Synch WSDL on a single PortType.
Both Operations include the Custom fault inside WSDL.
Inside the fault handler(catch), i am replying to the Custom Fault using reply action.
Irrespective of the Operation invoked from the front-end, i am replying on the First Operation of the PortTypeusing reply action.
When the fault occurs for the Second Operation , then also i am using the Operation as "First" inside the reply action inside the Fault Handler(catch) .
Still it is working for me.
Does operation name doesn't makes any difference while replying from fault handler(catch block).
I was not expecting the reply to work like this because i have selected the First Operation in reply action but the fault was caught from the Second Operation.
Wanted to know , OperationName doesn't makes any difference in reply action for the faults ?
Is it just the PortType which is significant ?