You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This turned out to be very brittle when VIES updated their SOAP envelope unexpectedly and SweetXml no longer had a correct path to access values in the responses.
SweetXml seems like it should be able to handle xpaths with no namespaces. If someone could get a prefix-independent path to work when SweetXml.xpath is called, that would be swell :)
Currently we have the XML namespace prefixes hard coded into our SweetXpath structs.
This turned out to be very brittle when VIES updated their SOAP envelope unexpectedly and
SweetXml
no longer had a correct path to access values in the responses.SweetXml seems like it should be able to handle xpaths with no namespaces. If someone could get a prefix-independent path to work when
SweetXml.xpath
is called, that would be swell :)The text was updated successfully, but these errors were encountered: