Details

    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      The work-around, which is to move all the XSD and WSDL files into the same directory and change all the imports

      Show
      The work-around, which is to move all the XSD and WSDL files into the same directory and change all the imports
    • Release Notes Text:
      Hide
      When services were deployed to JBoss Web Services Native, any XML Schema Declaration (XSD) imports with relative URLs were rewritten as absolute URLs relative to the WSDL service contract. This worked fine, unless an imported XSD imported a second XSD using a relative path. In this case, the path of the second XSD was incorrectly rewritten to be relative to the first XSD instead of the WSDL service contract. This problem has been resolved, and the paths are now rewritten relative to the WSDL service contract.
      Show
      When services were deployed to JBoss Web Services Native, any XML Schema Declaration (XSD) imports with relative URLs were rewritten as absolute URLs relative to the WSDL service contract. This worked fine, unless an imported XSD imported a second XSD using a relative path. In this case, the path of the second XSD was incorrectly rewritten to be relative to the first XSD instead of the WSDL service contract. This problem has been resolved, and the paths are now rewritten relative to the WSDL service contract.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      WSDL contains import for 2 XSDs
      The paths to both XSD imports are correct containing
      schemaLocation=http://127.0.0.1:8080/my-web-service/my-web-service/?wsdl&resource=../../../xsd/misc/my-first-import.xsd

      When using the link to my-first-import.xsd the content of it is presented and it contains further import of
      schemaLocation="http://127.0.0.1:8080/my-web-service/?wsdl&resource=../../external/xsd/misc/secondary-import.xsd"

      This one's path contains only "../../" and the link to it fails if it was "../../../../" sounds like a bug

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dlofthouse Darran Lofthouse
                  Reporter:
                  skoussou Stelios Koussouris
                  Writer:
                  Misty Stanley-Jones
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: