[
http://jira.jboss.com/jira/browse/JBWS-1969?page=all ]
Maarten Moens updated JBWS-1969:
--------------------------------
Attachment: console.log
Attached console log
Cannot publish wsdl with imported schema files, using bottom up
approach
------------------------------------------------------------------------
Key: JBWS-1969
URL:
http://jira.jboss.com/jira/browse/JBWS-1969
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-2.0.2
Reporter: Maarten Moens
Attachments: console.log, echo.ear, src.zip
When you create a Bottom up webservice and you normally want the existing wsdl to be used
by the deployed service.
On JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) combined
withjbossws-native-2.0.1.GA or jbossws-native-2.0.2.GA the deploy of a EJB webservice
endpoint with an wsdlLocation fails with the following error:
org.jboss.ws.WSException: Cannot publish wsdl to:
C:\<masked>\jbossxxx-node1\data\wsdl\echo.ear\echo-service.jar\echo\EchoService.wsdl
...
Caused by: java.io.IOException: Cannot get URL for: META-INF/wsdl//echo/EchoService.xsd
at org.jboss.wsf.common.URLLoaderAdapter.findChild(URLLoaderAdapter.java:106)
at
org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
If you don't use the hand written wsdl and let jboss generate it everything works
just fine.
The META-INF directory contains the following files:
META-INF/
wsdl/echo/
EchoService.wsdl
EchoService.xsd
When you place the Wsdl and xsd directly in the wsdl directory everything works fine.
However this is not an option because the real usecase is much more complicated with lots
of other schema files to import.
Sample code will be attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira