-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose the WSDL class #1071
Expose the WSDL class #1071
Conversation
While it is not a documented use case, the WSDL class can be used directly to (de-)serialize XML. This enables users to use an SOAP endpoint that does not expose bindings in the WSDL.
@ties this looks good. can you add documentation in the README? |
I added documentation in the readme. I do not know the project very well - I'm confident the example code works (it's modeled after my real usage), however it is probably useful if you double check that my interpretation of the functionality is correct. The usage of |
thanks! |
* Exposes the WSDL class While it is not a documented use case, the WSDL class can be used directly to (de-)serialize XML. This enables users to use an SOAP endpoint that does not expose bindings in the WSDL. * Document usage of the WSDL class in Readme.md
While it is not a documented use case, the WSDL class can be used
directly to (de-)serialize XML. This enables users to use an SOAP
endpoint that does not expose bindings in the WSDL.
In my specific use case, the SOAP endpoint is an interface to Microsoft Dynamics with URL's documented in documentation. The service can alledgedly be used directly by
svcutil.exe
, but is less idiomatic to consume from python or nodejs.I hope you will consider making the WSDL class part of the public API.