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
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).
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
The text was updated successfully, but these errors were encountered: