[SWS-575] CommonsXsdSchemaCollection: Combination of xs:includes and xs:imports in a schema result in incorrect/overcomplete schema in wsdl generated by DefaultWsdl11Definition Created: 12/Oct/09  Updated: 04/May/12  Resolved: 10/Jan/10

Status: Closed
Project: Spring Web Services
Component/s: XML
Affects Version/s: 1.5.8
Fix Version/s: 1.5.9

Type: Bug Priority: Minor
Reporter: Gisbert van Rossum Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 17m
Time Spent: 1h 43m
Original Estimate: 0.25d
Environment:

Not relevant, issue reproduced on both windows/jboss4.3 and Mac OS X 10.5.8/tomcat 6.0.18


Attachments: Zip Archive holidayService.zip    

 Description   

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).



 Comments   
Comment by Gisbert van Rossum [ 25/Nov/09 ]

holidayservice showing the issue

Comment by Arjen Poutsma [ 10/Jan/10 ]

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

Comment by Arjen Poutsma [ 10/Jan/10 ]

this should be fixed now.

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Mon Dec 11 13:00:12 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.