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
What's the best way to create an XML-document like this one with XMLParsing? It would be nice if we could enhance a struct to feature an optional qualifiedNamespace field that contains the namespace prefix (which would then be automatically inserted by the encoder) and the local name (URI, which could either be automatically scanned and inserted into the envelope, or manually).
The text was updated successfully, but these errors were encountered:
Hi @mickeyl, thank you for creating this issue. As far as I understand, XMLParsing is no longer maintained. I maintain a fork of this library, it's called XMLCoder and contains bugfixes and feature improvements. One of those is a namespaces flag that you could find helpful. If it doesn't work for your case, please let me know either here, or by opening an issue in the XMLCoder repository, I would be happy to improve the library so that it better serves all users.
I'd like to use this library for communicating with SOAP web-services. For those, you often encounter namespaces in SOAP requests, e.g.:
What's the best way to create an XML-document like this one with XMLParsing? It would be nice if we could enhance a struct to feature an optional
qualifiedNamespace
field that contains the namespace prefix (which would then be automatically inserted by the encoder) and the local name (URI, which could either be automatically scanned and inserted into the envelope, or manually).The text was updated successfully, but these errors were encountered: