Request to inline included XSD's in auto generated WSDL's [SWS-271]

[gregturn]

Eugene Westerhof opened SWS-271 and commented

The followIncludeImport only reads the included.xsd to find request and response elements. It doesn't inline the XSD, so you still end up with include statements. Some client software that uses WSDL's to generate code does not process include statements. It would therefore be handy to have the included XSD's inlined

---

Issue Links:

• add support for imported xsd in static wsdl as well as xsd's that import other xsd's [SWS-281] #438 add support for imported xsd in static wsdl as well as xsd's that import other xsd's

3 votes, 3 watchers

[gregturn]

Claus Ibsen commented

I second that. We use a older product that has problems with wsdl files with includes.

It should be configurable to use inline or not.

[gregturn]

Arjen Poutsma commented

This could only work for includes (i.e. schema's with the same namespace), and not imports (which can potentially have another namespace). Still, it's an interesting feature to add.

Overall, however, I think that the XsdBasedSoap11Wsdl4jDefinitionBuilder is getting too much features, and as a result is getting a pain to maintain. I am seriously thinking about refactoring the thing into separate classes, though currently I am unsure how to proceed with this.

[gregturn]

Arjen Poutsma commented

See my comment in #438 for my suggested solution to this issue.

[gregturn]

Arjen Poutsma commented

Closing issues in 1.5 RC1.

[gregturn]

Sagar commented

can you please provide the source for related this issue..