Skip to Content

SOAP Fault messages - SOAP Reciever


I'm running out of ideas on how to handle the SOAP faults. With the WSDL as in Here, there is not fault message defined

<wsdl:operation name="AnulacionLRDetOperacionIntracomunitaria">
<wsdl:input message="siiWdsl:EntradaAnulacionLRDetOperacionIntracomunitaria"/>
<wsdl:output message="siiWdsl:RespuestaAnulacionLRDetOperacionesIntracomunitarias"/>

The web service returns a SOAP fault for appication/data errors. Given the above definition, i'm not sure on how to handle the SOAP faults. Did try with couple of blogs from Jin Shin and others but i think that didnt help much.

Appreciate if i can get any help to get this done please.

The scenario i'm working is proxy to soap

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Jun 05, 2017 at 06:29 AM

    Hi Prabhu,

    If you give us some example we can help you better, for example with this example i unwrap map the fault messages:

    <xsl:stylesheet version="1.0">
        <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
        <xsl:template match="/">
            <ns0:RootElement xmlns:ns0="rootnamespace">
                    <xsl:when test=".//faultcode">
                                <xsl:value-of select=".//faultcode"/>
                                <xsl:value-of select=".//faultstring"/>
                                <xsl:value-of select=".//n0:elementFirst"/>


    Add comment
    10|10000 characters needed characters exceeded

  • Jun 02, 2017 at 06:03 AM

    Hi Prabhu,

    When i have scenario with SOAP fault and i need a map to sender, i usually follow this steps:

    1. On SOAP receiver i mark the check DO NOT USE SOAP ENVELOPE.

    2. I do the SOAP envelope manually with XSLT, for the request.

    3. I extract with XSLT the response, in this way in one XSLT i unwrap the SOAP tags and prepare for a second mapping the SOAP fault or the normal response without issues.


    Add comment
    10|10000 characters needed characters exceeded

    • Thanks for your response . That's what I have in place for (1) and (2).

      But when a fault message is received I think we can have a XSLT to catch the message but the main response structures cardinality is 1...1 which fails as the source element is not found in the response. Only the fault message is provided in case of data/application errors

      so how do I need to handle this?

  • Jun 02, 2017 at 10:58 AM

    Hi Prabhu,

    When the system is throwing back SOAP fault then please see the structure of the response.

    1. create a data type and message type with exact fault xml message PI is receiving from webservice. Say FaultMT

    2. Create a message mapping from FaultMT to Proxy expected response . let it be called FaultMM.

    3. Add FaultMM to both Outsound Service interface and Inbound service interface under fault mapping part.

    4. Add FaultMM to the operation mapping in the third tab of fault mapping.



    Add comment
    10|10000 characters needed characters exceeded

  • Jun 02, 2017 at 01:27 PM

    Hi Prabhu!

    In case of using XSLT transformation in response mapping, actually, there is no need to design any extended structures. You just check in XSLT what element exists in your response message and build response message to sender accordingly.

    Regards, Evgeniy.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Prabhu!

      When you call XSLT transformation against input message no schema validation is performed, so both normal response and SOAP Fault messages can be transformed. You just need to check which kind of element exists in input message: //Your_Response_Message_Type or //soap:Fault

      Regards, Evgeniy.