Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-3070

Secondary import of XSD contains incorrect path

XMLWordPrintable

    • 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

      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 "../../../../".

      ---------------------------------------------------------------------------------------------

      When an xsd contains an import with a relative URL the URL is relative to the specific schema.
      When accessing the WSDL and XSD after deployment to JBossWS all schemaLocations are replaced with an absolute URL: -
      http://localhost:8080/my-web-service/?wsdl&resource=../../../xsd/misc/internal-misc.xsd
      This URL contains a resource parameter which is the location of the .xsd relative to the wsdl, currently the relative part is being left relative to the xsd and not the wsdl.

            darran.lofthouse@redhat.com Darran Lofthouse
            skoussou Stelios Koussouris (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: