Announcement Announcement Module
Collapse
No announcement yet.
Handling multiple xsd's in wsdl Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    builder property for WSDL to inline included XSDd

    Hi Arjen

    Could tell us the name of the property that can be set to tell WSDLBuilder to inline the included XSD.


    Originally posted by Arjen Poutsma View Post
    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 a include statement.

    I suppose we could inline the schema with an include (yet another property for the XsdBasedSoap11Wsdl4jDefinitionBuilder ), but we can't do this for imports, because they can have another target namespace.

    Comment


    • #32
      This problem (getting a SAX Exception while importing a WSDL from URL to SOAP UI) is related to the fact that your schema is not publicly accessible from your WEB-INF. Make sure that you schema is publicly accessible from WEB-INF.

      Comment


      • #33
        Originally posted by Arjen Poutsma View Post
        Issue SWS-271 created

        Comment

        Working...
        X