WSDL imports are not replaced with absolute path ------------------------------------------------- Key: JBWS-2206 URL: http://jira.jboss.com/jira/browse/JBWS-2206 Project: JBoss Web Services Issue Type: Bug Security Level: Public(Everyone can see) Components: jbossws-metro Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-metro-3.0.2 Attachments: example.zip Mathias wrote: When using @WebService.wsdlLocation on a EJB3 endpoint implementation class to point to a local WSDL file with schema imports with relative schemaLocation paths, the schemaLocation paths are still not replaced by the absolute path in the published WSDL. Please, see the attached source for an example on how to get this problem. I'm using JBoss AS 4.2.2 with JBossWS 3.0.1-Metro1 .0.1.

WSDL imports are not replaced with absolute path ------------------------------------------------- Key: JBWS-2206 URL: http://jira.jboss.com/jira/browse/JBWS-2206 Project: JBoss Web Services Issue Type: Bug Security Level: Public(Everyone can see) Components: jbossws-metro Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Attachments: example.zip Mathias wrote: When using @WebService.wsdlLocation on a EJB3 endpoint implementation class to point to a local WSDL file with schema imports with relative schemaLocation paths, the schemaLocation paths are still not replaced by the absolute path in the published WSDL. Please, see the attached source for an example on how to get this problem. I'm using JBoss AS 4.2.2 with JBossWS 3.0.1-Metro1 .0.1.

WSDL imports are not replaced with absolute path ------------------------------------------------- Key: JBWS-2206 URL: http://jira.jboss.com/jira/browse/JBWS-2206 Project: JBoss Web Services Issue Type: Bug Security Level: Public(Everyone can see) Components: jbossws-metro Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-metro-3.0.4 Attachments: example.zip Mathias wrote: When using @WebService.wsdlLocation on a EJB3 endpoint implementation class to point to a local WSDL file with schema imports with relative schemaLocation paths, the schemaLocation paths are still not replaced by the absolute path in the published WSDL. Please, see the attached source for an example on how to get this problem. I'm using JBoss AS 4.2.2 with JBossWS 3.0.1-Metro1 .0.1.

WSDL imports are not replaced with absolute path ------------------------------------------------- Key: JBWS-2206 URL: https://jira.jboss.org/jira/browse/JBWS-2206 Project: JBoss Web Services Issue Type: Bug Security Level: Public(Everyone can see) Components: jbossws-metro Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assignee: Alessio Soldano Fix For: jbossws-metro-3.0.5 Attachments: example.zip Mathias wrote: When using @WebService.wsdlLocation on a EJB3 endpoint implementation class to point to a local WSDL file with schema imports with relative schemaLocation paths, the schemaLocation paths are still not replaced by the absolute path in the published WSDL. Please, see the attached source for an example on how to get this problem. I'm using JBoss AS 4.2.2 with JBossWS 3.0.1-Metro1 .0.1.