Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-271

Request to inline included XSD's in auto generated WSDL's

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5 RC1
    • Component/s: None
    • Labels:
      None

      Description

      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

          Activity

          Hide
          davsclaus Claus Ibsen added a comment -

          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.

          Show
          davsclaus Claus Ibsen added a comment - 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.
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          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.

          Show
          arjen.poutsma Arjen Poutsma added a comment - 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.
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          See my comment in SWS-281 for my suggested solution to this issue.

          Show
          arjen.poutsma Arjen Poutsma added a comment - See my comment in SWS-281 for my suggested solution to this issue.
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Closing issues in 1.5 RC1.

          Show
          arjen.poutsma Arjen Poutsma added a comment - Closing issues in 1.5 RC1.
          Hide
          sagardasari Sagar added a comment -

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

          Show
          sagardasari Sagar added a comment - can you please provide the source for related this issue..

            People

            • Assignee:
              arjen.poutsma Arjen Poutsma
              Reporter:
              eugene westerhof Eugene Westerhof
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: