SOA Suite: SOAP Faults in BPEL and Mediator by Martien van den Akker
In the past few months, at our current customer we are having a “robustness project” to improve our SOA Suite implementation. We had a lot of duplication and it turned out that we had a lot of WSDLs in our composite projects. Many of those are a result of BPEL projects from 10g. But some of them weren’t possible to move because it would break the project.
The first projects where I encountered the problem were projects with Mediators. After moving the WSDLs to MDS, most of our SoapUI/ReadyAPI unit test worked, except for those simulating a SOAP Fault. It seemed that the Mediator could not map the SOAP Fault. I searched “me an accident”, we would say in Holland. But without any luck. Actually, I can’t find any documents that talks about catching SOAP Faults in SOASuite. Which is a weird thing, because in BPM Suite, sharing the same soa-infra and process engine, there is a preference for SOAP Faults. Because BPM can react with specific exception transitions on SOAP Faults.
So what is this weird behavior? Well actually, SOA Suite, apparently both BPEL and Mediator, interpret SOAP Faults as Remote Faults! So, in BPEL you can’t catch it as a SOAP Fault and Mediator can’t route it in the correct way. What you would suggest from the UI. However, just now I found a solution. That is, I found it earlier for Mediator, but couldn’t explain it. Since the same behavior can be seen in BPEL as well, I can write down my story. Read the complete article here.
For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.