Namespaces declared in Soap:Envelope ignored when comparing SOAP response with expected value

[bouncysteve]

I am testing a soap service which sometimes returns nil elements, defined in xsi namespace. Unlike issue #754, the xsi namespace is defined in the response, it is declared in the soap envelope, so that this test using locally defined xml will pass:

Scenario:

        * def content =
        """
        <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <soap:Body>
        <GetNextDeparturesResponse xmlns="http://gndrurl">
        <DeparturesBoard
        xmlns:c6="http://c6url"
        xmlns:t13="http://t13url">
        <t13:destination>
        <t13:service xsi:nil="true"/>
        </t13:destination>
        </DeparturesBoard>
        </GetNextDeparturesResponse>
        </soap:Body>
        </soap:Envelope>
        """

        * def content2 =
        """
        <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <soap:Body>
        <GetNextDeparturesResponse xmlns="http://gndrurl">
        <DeparturesBoard
        xmlns:c6="http://c6url"
        xmlns:t13="http://t13url">
        <t13:destination>
        <t13:service xsi:nil="true"/>
        </t13:destination>
        </DeparturesBoard>
        </GetNextDeparturesResponse>
        </soap:Body>
        </soap:Envelope>
        """
        
        * match content == content2

However, a scenario where a SOAP request produces the same XML in the response will fail on the match statement:

 ...
 Then match soapCall.response == content2
 ...
javax.xml.transform.TransformerException: java.lang.RuntimeException: Namespace for prefix 'xsi' has not been declared.

This looks like a problem in the handling of the response when used in match, as if it is being treated differently to any other xml document, perhaps by stripping the soap wrapper from both documents before comparing, so that the xsi namespace declaration is lost?

Note that this problem happens regardless of the value of xmlNamespaceAware

[ptrthomas]

thanks for the repro. you may have seen this already, but a workaround could be to manually strip / modify the namespace data from the XML: https://stackoverflow.com/a/75626292/143475

[bouncysteve]

Thanks Peter, I would use that, but in this case we've made a change around the xsi:nil, so I was asked to explicitly test for it being included. I'm off for Christmas now, but I'll see if I can find a fix when I'm back.

…

On Fri, 22 Dec 2023, at 3:12 PM, Peter Thomas wrote: thanks for the repro. you may have seen this already, but a workaround could be to manually strip / modify the namespace data from the XML: https://stackoverflow.com/a/75626292/143475 — Reply to this email directly, view it on GitHub <#2469 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4QSWDZ7OB4XIKR5NJKCSTYKWPNBAVCNFSM6AAAAABA74FH4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXG44TOOJZGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>