-
Notifications
You must be signed in to change notification settings - Fork 392
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
Compliant WSDL doesn't parse some constants and nested complexType objects correctly #16
Comments
hm, looks like an issue indeed. I'm looking into it. |
@beckler I'm still working on this, that WSDL uncovered a couple of issues with attributes. Also, the schema doesn't reuse complex types but instead it embeds them inside elements which is kind of wacky but still valid XSD. |
@beckler what I'm planing to do is to unwrap the embedded complex types since they are not being re-used anywhere else, leaving their fields become part of the parent type. This causes some clashes with existing attributes in the parent type so I'll see what I can do to fix that too. |
This WSDL is SOAP 1.1, and claims to be WS-I 1.0 compliant, but gowsdl can't seem to handle some of the objects that are nested complexTypes. The formatter fails because some types don't seem to be parsed correctly.
These are two general examples I have been running into:
This may be a limitation of the project that I'm just not aware of, but I figured I would raise an issue just in case.
The text was updated successfully, but these errors were encountered: