[jbossws-issues] [JBoss JIRA] (JBWS-3655) wsdlLocation in ejb-jar throws error for schema import

[Mustafa Musaji (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mustafa Musaji updated JBWS-3655:
---------------------------------

    Attachment: awesome.zip

    
> wsdlLocation in ejb-jar throws error for schema import
> ------------------------------------------------------
>
>                 Key: JBWS-3655
>                 URL: https://issues.jboss.org/browse/JBWS-3655
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: jbossws-cxf-4.1.3
>            Reporter: Mustafa Musaji
>            Assignee: Jim Ma
>         Attachments: awesome.zip
>
>
> The use case is as follows:
> EAR that contains EJB-JAR and JAR. The JAR contains wsdl in META-INF but referenced from wsdlLocation in EJB-JAR to avoid JBoss generating it's own WSDL without external schema). On deployment the error we get is:
> {noformat}
> Caused by: java.io.IOException: JBAS015526: Child 'META-INF/wsdl/Awesome_schema1.xsd' not found for VirtualFile: "/content/awesome.ear/awesome-ejb-0.0.1-SNAPSHOT.jar"
>         at org.jboss.as.webservices.util.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:61)
>         at org.jboss.as.webservices.util.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:71)
>         at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:76)
>         at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:228)
>         at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:253)
>         at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:257)
>         at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:92)
>         ... 14 more
> {noformat}
> Removing the wsdlLocation from the ejb-jar fixes this but the use case is that JBoss should be able to load the schema from the classpath since the wsdl was loaded from the classpath.
> I will attach a test case to the JIRA to replicate this behaviour. It's a maven build that use cxf-java2ws-plugin to generate the xsd imports and WSDL in the JAR file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira