XML Namespaces Injection Change Causing Unexpected Results

[aedryan]

Due to the change to inject all namespaces into the built XML, I'm seeing unexpected results in an API I am integrating with. It appears that prior to this change the xmlns and xmlns:soap namespaces were not included in the built XML despite their inclusion in my WSDL configuration. Now they are included and they appear to be clobbering something in the external API I'm integrating with. If I remove them from my WSDL config, the Savon client fails to find the operations and build anything.

I can find no callbacks, actions, or any way to get in between Savon and the builder of the XML except to manually build the XML and call the API using some of Savon's exposed classes.

I realize this is a bit of a funny issue to report and is likely the external API I'm integrating with that is at fault here, I can really only provide the XSD I have for that which is here: https://vintelligence.ihsmarkit.com/vindecoder/VinDecoderService_schema1.xsd

If I had some way to get in between the XML building when calling an operation from the client or some setting to more explicitly control which namespaces are injected into the build XML that would help me move past this issue.