[JBoss JIRA] (JBWS-3571) SOAPAddressWSDLParser does not process wsdl imports
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBWS-3571?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBWS-3571:
-----------------------------------------------
Mustafa Musaji <mmusaji(a)redhat.com> made a comment on [bug 916944|https://bugzilla.redhat.com/show_bug.cgi?id=916944]
Created one off patch for changed depending on jbossws cxf. https://svn.jboss.org/repos/jbossws/thirdparty/cxf/branches/cxf-2.4.9.jbo...
> SOAPAddressWSDLParser does not process wsdl imports
> ---------------------------------------------------
>
> Key: JBWS-3571
> URL: https://issues.jboss.org/browse/JBWS-3571
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.1.1
>
>
> The SOAPAddressWSDLParser currently does not process wsdl imports, so it basically misses soap:address entries corresponding to bindings living in imported wsdl docs.
--
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
11 years, 9 months
- 1
- 0
[JBoss JIRA] (JBWS-3571) SOAPAddressWSDLParser does not process wsdl imports
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBWS-3571?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBWS-3571:
-----------------------------------------------
Mustafa Musaji <mmusaji(a)redhat.com> made a comment on [bug 916944|https://bugzilla.redhat.com/show_bug.cgi?id=916944]
Description of problem:
SOAPAddressWSDLParser does not process wsdl imports
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
> SOAPAddressWSDLParser does not process wsdl imports
> ---------------------------------------------------
>
> Key: JBWS-3571
> URL: https://issues.jboss.org/browse/JBWS-3571
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.1.1
>
>
> The SOAPAddressWSDLParser currently does not process wsdl imports, so it basically misses soap:address entries corresponding to bindings living in imported wsdl docs.
--
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
11 years, 9 months
- 1
- 0
[JBoss JIRA] (JBWS-3605) Cannot publish wsdl with imported schema files, using bottom up approach
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3605?page=com.atlassian.jira.plugin.... ]
Alessio Soldano edited comment on JBWS-3605 at 3/1/13 2:27 AM:
---------------------------------------------------------------
The wsdl and xsd you used should have been attached to allow reproducing. In any case, we have no further development planned in community for the jbossws-native stack, hence closing this issue. If you're on a enterprise product, please fill in a bug report through your customer support channel, otherwise simply move to JBossWS 4 (jbossws-cxf stack) and AS 7.1 or greater.
was (Author: asoldano):
The wsdl and xsd you used should have been attached to allow reproducing. In any case, we have now further development planned in community for the jbossws-native stack, hence closing this issue. If you're on a enterprise product, please fill in a bug report through your customer support channel, otherwise simply move to JBossWS 4 (jbossws-cxf stack) and AS 7.1 or greater.
> Cannot publish wsdl with imported schema files, using bottom up approach
> ------------------------------------------------------------------------
>
> Key: JBWS-3605
> URL: https://issues.jboss.org/browse/JBWS-3605
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Reporter: Saravanan Navaneethan
> Assignee: Alessio Soldano
>
> I still see the same issue in jbossws-native-3.0.5.GA as mentioned in JBWS-1969.
> Here is my wsdl structure
> META-INF/
> wsdl/partservice/
> CatalogVendor.Core.PartService.wsdl
> CatalogVendor.Core.PartService.xsd
> I got this error message.
> org.jboss.ws.WSException: Cannot publish wsdl to: C:\Jboss-4.2.0.GABIMS\jboss-as\server\default\data\wsdl\GOLD.ear\GOLD-WS.war\CatalogVendor.Core.PartService.wsdl
> at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:142)
> at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.start(PublishContractDeploymentAspect.java:50)
> at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129)
> at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
> at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
> at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
> at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
> at org.jboss.Main.boot(Main.java:200)
> at org.jboss.Main$1.run(Main.java:518)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.io.IOException: Cannot get URL for: WEB-INF/wsdl/CatalogVendor.Core.PartService.xsd
> at org.jboss.wsf.common.URLLoaderAdapter.findChild(URLLoaderAdapter.java:114)
> at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:97)
> -----------------------------------------------------------------------------------------------------
> -----------------------------------------------------------------------------------------------------
> Original issue - cloned:
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
- 1
- 0