-
Notifications
You must be signed in to change notification settings - Fork 159
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
strong-soap: Wrong sequence of xsd imports in wsdl leads to error #146
Comments
@PaulHindenberg Can you verify if #147 fixes your problem? |
@raymondfeng Yes, this fixes my issue, thanks Raymond. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
Description/Steps to reproduce
Firstly, I think this might be a bug since e.g. SOAP UI is able to parse the original WSDL and strong-soap returns an error.
The error appears while loading the WSDL with createClient(). Nothing special here.
The provided WSDL has 3 schema imports.
I was able to find a workaround by switching the xsd imports on position 1 & 2. So, the following is not leading to an error while everything else stays the same:
In this archive testcase.zip you can find the broken and the working version of the wsdl and xsd files. Again, just the positions of the type imports were changed to .
"dependencies": { "strong-soap": "^1.5.0" }
If bug: Steps to reproduce:
`var options = {};
Expected result
No error and a working client Object
Additional information
The text was updated successfully, but these errors were encountered: