SOA 11g: How To Populate The "detail" Element In A SOAP Fault
(Doc ID 1351698.1)
Last updated on APRIL 23, 2019
Applies to:
Oracle(R) BPEL Process Manager 10g - Version 10.1.2.0.0 and laterInformation in this document applies to any platform.
***Checked for relevance on 25-Aug-2011***
Goal
When a catch block in used in BPEL component, it catches the errors and forwards the fault message to caller.
There may be difficulties when attempting to map the "detail" element in SOAP Fault
because the error is populated in "faultstring" element instead of "detail" element as shown below:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>
faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://xmlns.oracle.com/Queries/FaultProject/BPELProcess1}FaultMessage}
parts: {{
payload=<processResponse xmlns="http://xmlns.oracle.com/Queries/FaultProject/BPELProcess1">
<result>remoteFault</result>
</processResponse>}
</faultstring>
<faultactor/>
<detail>
<exception/>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>
faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://xmlns.oracle.com/Queries/FaultProject/BPELProcess1}FaultMessage}
parts: {{
payload=<processResponse xmlns="http://xmlns.oracle.com/Queries/FaultProject/BPELProcess1">
<result>remoteFault</result>
</processResponse>}
</faultstring>
<faultactor/>
<detail>
<exception/>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |