Resolution:
Abstract:
==========
How to analyze multi-part soap fault data?

Description:
==========
If you receive the following soap:Fault message, you will encounter unexpected behavior in BW:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soap:Body>
        <soap:Fault>
            <faultcode xmlns="">detail</faultcode>
            <faultstring xmlns="">Shopper with shopperId:12345678 does not exist</faultstring>
            <detail xmlns="">
                <code xmlns="">209</code>
                <description xmlns="">Unable to find shopper from the specified ShopperId</description>
            </detail>
        </soap:Fault>
    </soap:Body>
</soap:Envelope>

There is some multiple part in the Fault detail element, but BW doesn’t support that.

Environment:
==========
TIBCO ActiveMatrix BusinessWork / All

Symptoms:
==========
There is unexpected behavior receiving multiple part soap fault messages in BW.

Cause:
==========
It is WSDL 1.1 specification limits that soap:Fault message can only have one part. Refer to http://www.w3.org/TR/wsdl#_soap:fault for details, it says:"The fault message MUST have a single part."

Resolution:
==========
Use a workaround such as an HTTP proxy implemented in BW. See attachment (Filename:multiPart_soapFault.zip).

Attachments:
==========
multiPart_soapFault.zip