-
Bug
-
Resolution: Done
-
Major
-
jbossws-cxf-4.1.3
-
None
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:
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
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.
- relates to
-
JBWS-3904 WSDL contract retrieval enhancement and early availability check
-
- Closed
-
