The SOAP Faultcode and Faultstring Information Not Propagated Properly to Application (Doc ID 1072049.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle Communications Services Gatekeeper - Version: 4.1.1 and later   [Release: 4.1 and later ]
Information in this document applies to any platform.
Checked for relevance on 08-Dec-2011

Symptoms

For SOAP2SOAP plugin, OCSG 4.1.1 does not propagate the SOAP fault information properly. The field faultcode is populated incorrectly, whereas faultstring is not populated at all. Below is the example response received:

<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring/>
<detail>
<exam:InsufficientFundFault xmlns:exam="http://example">
<exam:balance>111</exam:balance>
<exam:requestedFund>222</exam:requestedFund>
</exam:InsufficientFundFault>
</detail>
</env:Fault>

Besides, the undefined exception is not transferred transparently.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms