[
https://jira.jboss.org/browse/JBWS-3070?page=com.atlassian.jira.plugin.sy...
]
Darran Lofthouse updated JBWS-3070:
-----------------------------------
Fix Version/s: jbossws-native-4.0
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
"../../../../".
---------------------------------------------------------------------------------------------
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...
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.
was:
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
Affects: (was: [Release Notes])
Secondary import of XSD contains incorrect path
-----------------------------------------------
Key: JBWS-3070
URL:
https://jira.jboss.org/browse/JBWS-3070
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Stelios Koussouris
Assignee: Darran Lofthouse
Fix For: jbossws-native-4.0
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...
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira