February 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3605) Cannot publish wsdl with imported schema files, using bottom up approach

by Saravanan Navaneethan (JIRA)

[ https://issues.jboss.org/browse/JBWS-3605?page=com.atlassian.jira.plugin.... ] Saravanan Navaneethan updated JBWS-3605: ---------------------------------------- Description: 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. was: I still see the same issue in jbossws-native-3.0.5.GA. Here is my wsdl structure META-INF/ wsdl/partservice/ CatalogVendor.Core.PartService.wsdl CatalogVendor.Core.PartService.xsd I got 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. > 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: Magesh Bojan > > 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
0 / 0

[JBoss JIRA] (JBWS-3605) Cannot publish wsdl with imported schema files, using bottom up approach

by Saravanan Navaneethan (JIRA)

[ https://issues.jboss.org/browse/JBWS-3605?page=com.atlassian.jira.plugin.... ] Saravanan Navaneethan updated JBWS-3605: ---------------------------------------- Description: I still see the same issue in jbossws-native-3.0.5.GA. Here is my wsdl structure META-INF/ wsdl/partservice/ CatalogVendor.Core.PartService.wsdl CatalogVendor.Core.PartService.xsd I got 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. was: 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. > 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: Magesh Bojan > > I still see the same issue in jbossws-native-3.0.5.GA. > Here is my wsdl structure > META-INF/ > wsdl/partservice/ > CatalogVendor.Core.PartService.wsdl > CatalogVendor.Core.PartService.xsd > I got > 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
0 / 0

[JBoss JIRA] (JBWS-3605) Cannot publish wsdl with imported schema files, using bottom up approach

by Saravanan Navaneethan (JIRA)

Saravanan Navaneethan created JBWS-3605: ------------------------------------------- Summary: 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: Magesh Bojan 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
0 / 0

[JBoss JIRA] (JBWS-1969) Cannot publish wsdl with imported schema files, using bottom up approach

by Saravanan Navaneethan (JIRA)

[ https://issues.jboss.org/browse/JBWS-1969?page=com.atlassian.jira.plugin.... ] Saravanan Navaneethan commented on JBWS-1969: --------------------------------------------- I still see this issue in jbossws-native-3.0.5.GA I have wsdl with import xsd. The imported xsd imported other xsd. I still get exactly same error as reported in original bug > Cannot publish wsdl with imported schema files, using bottom up approach > ------------------------------------------------------------------------ > > Key: JBWS-1969 > URL: https://issues.jboss.org/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 > Assignee: Magesh Bojan > Fix For: jbossws-native-3.0.1 > > Attachments: console.log, echo.ear, src.zip > > Time Spent: 6 hours > Remaining Estimate: 0 minutes > > 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
0 / 0

[JBoss JIRA] (JBWS-3604) Generated wsdl soap access incorrect for classes implementing multiple wsdls

by Alex O (JIRA)

Alex O created JBWS-3604: ---------------------------- Summary: Generated wsdl soap access incorrect for classes implementing multiple wsdls Key: JBWS-3604 URL: https://issues.jboss.org/browse/JBWS-3604 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: Alex O I have a WSDL which defines 1 service that implements 2 portTypes. The address in the generated WSDL's soap:address section for only one of the port's is correct. The other remains the default value from the original WSDL -- 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
0 / 0

[JBoss JIRA] (JBWS-3603) JBossWS client configuration not working on Dispatch

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3603: ------------------------------------- Summary: JBossWS client configuration not working on Dispatch Key: JBWS-3603 URL: https://issues.jboss.org/browse/JBWS-3603 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2 The jbossws client configuration setup (either handlers or properties) is currently working for ports only, not for dispatches. -- 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
0 / 0

[JBoss JIRA] (JBWS-3602) Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3602?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3602: ---------------------------------- Description: The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. This is only reproducible using the jbossws-cxf integration w/ spring and having an endpoint whose address declaration in jbossws-cxf.xml is different from the computed address (context + url pattern) was:The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. > Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module > --------------------------------------------------------------------------- > > Key: JBWS-3602 > URL: https://issues.jboss.org/browse/JBWS-3602 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.2 > > > The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. > This is only reproducible using the jbossws-cxf integration w/ spring and having an endpoint whose address declaration in jbossws-cxf.xml is different from the computed address (context + url pattern) -- 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
0 / 0

[JBoss JIRA] (JBWS-3602) Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3602: ------------------------------------- Summary: Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module Key: JBWS-3602 URL: https://issues.jboss.org/browse/JBWS-3602 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Priority: Minor Fix For: jbossws-cxf-4.2 The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. -- 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
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3601: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 913411|https://bugzilla.redhat.com/show_bug.cgi?id=913411] Fix Versions for CXF-4790 are 2.8.0, 2.7.4, 2.6.7, 2.5.10 EAP 6.1.0 DR4 is using 2.6.6, version 2.6.7 was not yet released If this should be included in EAP 6.1.0, jboss-eap-6.1.0 flag must be selected to enter 3-ACK process. > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Labels: cxf > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3601: ----------------------------------------------- Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug 913411|https://bugzilla.redhat.com/show_bug.cgi?id=913411] Description of problem: Platform BZ for https://issues.jboss.org/browse/JBWS-3601 Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render <soapenv:Subcode>: import javax.xml.soap.SOAPConstants; import javax.xml.soap.SOAPFactory; import javax.xml.soap.SOAPFault; import javax.xml.ws.soap.SOAPFaultException; ... SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); ... throw new SOAPFaultException(fault); > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Labels: cxf > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2013