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

CommonsXsdSchemaCollection: Combination of xs:includes and xs:imports in a schema result in incorrect/overcomplete schema in wsdl generated by DefaultWsdl11Definition [SWS-575] #695

Closed
gregturn opened this issue Oct 12, 2009 · 4 comments
Assignees
Milestone

Comments

@gregturn
Copy link
Member

Gisbert van Rossum opened SWS-575 and commented

When using a DefaultWsdl11Definition for wsdl generation I used a CommonsXsdSchemaCollection to combine a set of xsd's. I found out that when a schema uses a mix of xs:imports and xs:includes, the inline schema in the generated wsdl (inside wsdl:types) contains an error. Both xs:imports and xs:includes are 'expanded' inline in the generated wsdl, but the xs:include lines are not removed from the inline schema, causing test tools like SOAPUI to fail (included schema's cannot be retrieved).


Affects: 1.5.8

Attachments:

Referenced from: commits 3091109

@gregturn
Copy link
Member Author

Gisbert van Rossum commented

holidayservice showing the issue

@gregturn
Copy link
Member Author

Arjen Poutsma commented

It seems that if I put the include before the import in hr.xsd, all works well.

@gregturn
Copy link
Member Author

Arjen Poutsma commented

this should be fixed now.

@gregturn
Copy link
Member Author

gregturn commented May 4, 2012

Arjen Poutsma commented

Closing old issues

@gregturn gregturn closed this as completed May 4, 2012
@gregturn gregturn added this to the 1.5.9 milestone Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants