Skip to content
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

Merged
merged 2 commits into from
Jun 7, 2019
Merged

Expose the WSDL class #1071

merged 2 commits into from
Jun 7, 2019

Conversation

ties
Copy link
Contributor

@ties ties commented May 31, 2019

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.

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.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.004%) to 93.37% when pulling e89bf50 on ties:feature/expose_wsdl into 7c832ed on vpulim:master.

@coveralls
Copy link

coveralls commented May 31, 2019

Coverage Status

Coverage increased (+0.004%) to 93.37% when pulling 06e0e85 on ties:feature/expose_wsdl into 7c832ed on vpulim:master.

@jsdevel
Copy link
Collaborator

jsdevel commented May 31, 2019

@ties this looks good. can you add documentation in the README?

@ties
Copy link
Contributor Author

ties commented Jun 7, 2019

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 objectToXML over objectToRpcXML or objectToDocumentXML was the first one I started using after switching from Jsonix after that was not compatible with some types in my WSDL...

@jsdevel jsdevel merged commit be79b70 into vpulim:master Jun 7, 2019
@jsdevel
Copy link
Collaborator

jsdevel commented Jun 7, 2019

thanks!

Danail-Irinkov pushed a commit to Danail-Irinkov/node-soap that referenced this pull request Jan 19, 2020
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants