Page 4 of 4 FirstFirst ... 234
Results 31 to 33 of 33

Thread: Handling multiple xsd's in wsdl

  1. Dec 13th, 2007, 03:36 AM #31
    sonubansal
    sonubansal is offline Junior Member
    Join Date
    Dec 2007
    Posts
    1

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


    Quote 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.
    Reply With Quote Reply With Quote
  2. Dec 28th, 2007, 03:17 PM #32
    bkalali
    bkalali is offline Junior Member
    Join Date
    Jul 2007
    Posts
    26

    Default

    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.
    Reply With Quote Reply With Quote
  3. Jan 16th, 2008, 02:26 AM #33
    Eugene Westerhof
    Eugene Westerhof is offline Junior Member
    Join Date
    Nov 2007
    Posts
    3

    Default

    Quote Originally Posted by Arjen Poutsma View Post
    Please create a JIRA issue at http://opensource.atlassian.com/proj...ing/browse/SWS
    Issue SWS-271 created
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules