November 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2840) Implement support for SOAP protocol in wsprovide

by Richard Opalka (JIRA)

Implement support for SOAP protocol in wsprovide ------------------------------------------------ Key: JBWS-2840 URL: https://jira.jboss.org/jira/browse/JBWS-2840 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-metro-3.2.2, jbossws-cxf-3.2.2, jbossws-native-3.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2842) Soap address rewrite does not use request url port when jbossws.undefined.host is setup

by Alessio Soldano (JIRA)

Soap address rewrite does not use request url port when jbossws.undefined.host is setup --------------------------------------------------------------------------------------- Key: JBWS-2842 URL: https://jira.jboss.org/jira/browse/JBWS-2842 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.0 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.2 After the changes for JBWS-2370, when providing jbossws.undefined.host setup to have the soap:address rewritten with the request url data, the port number is not taken from the request url anymore. While fixing this, we should provide a comprehensive test case for the WSDLRequestHandler rules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2841) ClassCastException TextImpl cannot be cast to SOAPElementImpl in CommonSOAPBinding.getParameterFromMessage

by Darran Lofthouse (JIRA)

ClassCastException TextImpl cannot be cast to SOAPElementImpl in CommonSOAPBinding.getParameterFromMessage ---------------------------------------------------------------------------------------------------------- Key: JBWS-2841 URL: https://jira.jboss.org/jira/browse/JBWS-2841 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.2 The following exception is reported on an invalid message: - 14:46:03,958 ERROR [SOAPFaultHelperJAXWS] SOAP request exception java.lang.ClassCastException: org.jboss.ws.core.soap.TextImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementImpl at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:896) at org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBinding.java:363) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:197) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:503) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:300) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:208) The ClassCastException is causing the correct exception to be missed: - if (soapContentElement == null && optional == false) throw new WSException("Cannot find child element: " + xmlName); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2839) Remove jboss.local.repository support

by Richard Opalka (JIRA)

Remove jboss.local.repository support ------------------------------------- Key: JBWS-2839 URL: https://jira.jboss.org/jira/browse/JBWS-2839 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-metro-3.2.2, jbossws-cxf-3.2.2, jbossws-native-3.2.2 This is old approach not used anymore. We're using maven repositories only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2511) Metro 3.0.5 install does not find SAAJMetaFactoryImpl class on Jboss 5.0 bootup

by Bryan Kearney (JIRA)

Metro 3.0.5 install does not find SAAJMetaFactoryImpl class on Jboss 5.0 bootup ------------------------------------------------------------------------------- Key: JBWS-2511 URL: https://jira.jboss.org/jira/browse/JBWS-2511 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.0.5 Environment: Jboss 5.0, sun jdk 1.6.11, running on Fedora 10, kernel 2.6.27.9-159.fc10.i686 Reporter: Bryan Kearney When installing metro, the bootup removes the jbossws-native.jar file from the jbossws.deployers directory. This is is the only location of the SAAJMetaFactoryImpl in the default server. Resoring this jar allows Metro to boot up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBWS-2837) ClassNotFoundException [SAAJMetaFactoryImpl] deploying a Webservice with Metro Stack 3.1.1

by Andreas Wuest (JIRA)

ClassNotFoundException [SAAJMetaFactoryImpl] deploying a Webservice with Metro Stack 3.1.1 ------------------------------------------------------------------------------------------ Key: JBWS-2837 URL: https://jira.jboss.org/jira/browse/JBWS-2837 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.1.1 Environment: Windows Vista Java jdk1.6.0_04 jboss-4.2.3.GA-jdk6 (Java 6 Version!) jboss-ws-metro-3.1.1:GA Reporter: Andreas Wuest Hi, i cannot deploy webservices using the Java 6 Version of jboss 4.2.3 and the Metro Stack in Version 3.1.1. Deployig the Webservice results in the following exception. I have never had problems with the java 5 Versions of JBoss ! 2009-11-23 11:55:07,567 [ERROR] [main] org.jboss.deployment.MainDeployer: Could not start deployment: file:/C:/NONBKU/JBoss/jboss-4.2.3.GA/server/default/tmp/deploy/tmp64242backend-0.1-SNAPSHOT.ear-contents/backend-process-0.1-SNAPSHOT.jar javax.xml.ws.WebServiceException: Failed to build METRO runtime model at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.start(RuntimeModelDeploymentAspect.java:133) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:95) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:88) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy34.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ExceptionInInitializerError at com.sun.xml.ws.api.BindingID.<clinit>(BindingID.java:321) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.createBinding(DeploymentDescriptorParserExt.java:350) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parseAdapters(DeploymentDescriptorParserExt.java:285) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parse(DeploymentDescriptorParserExt.java:171) at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.start(RuntimeModelDeploymentAspect.java:109) ... 78 more Caused by: java.lang.IllegalStateException: Failed to load javax.xml.soap.MetaFactory: org.jboss.ws.core.soap.SAAJMetaFactoryImpl at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:131) at javax.xml.soap.SAAJMetaFactory.getInstance(SAAJMetaFactory.java:60) at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:106) at com.sun.xml.ws.api.SOAPVersion.<init>(SOAPVersion.java:178) at com.sun.xml.ws.api.SOAPVersion.<clinit>(SOAPVersion.java:83) ... 83 more Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.core.soap.SAAJMetaFactoryImpl at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:125) ... 87 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2836) Remove unused jbossws-cxf.sar resources

by Alessio Soldano (JIRA)

Remove unused jbossws-cxf.sar resources --------------------------------------- Key: JBWS-2836 URL: https://jira.jboss.org/jira/browse/JBWS-2836 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.2.2 We have resources in server module that are not actually used. The (almost identical[*]) ones coming from jbossws-cxf-client.jar are the effective ones. To simplify the Apache CXF version update we should remove the useless ones. [*] the only change is in the logging interceptors that were automatically enable in an ancient version of JBossWS-CXF, but that we can't enable by default as that would be too verbose. Hence leaving that option to the user who can always modify the cxf.extension manually. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2822) JAX-WS Client endpoint configuration in jbossws-cxf.xml is ignored

by Alexandros Karypidis (JIRA)

JAX-WS Client endpoint configuration in jbossws-cxf.xml is ignored ------------------------------------------------------------------ Key: JBWS-2822 URL: https://jira.jboss.org/jira/browse/JBWS-2822 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.2.0 Environment: Windows XP 32bit, Sun JDK 1.6.0_16, JBoss AS 5.1.0.GA with JBossWS-CXF 3.2.0.GA Reporter: Alexandros Karypidis Normally, in order to configure endpoints and clients in CXF you use Spring's beans.xml. While this works for service provider endpoints, it is ignored for client stubs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2835) Remove deployers ordering workaround forAS 6.x series

by Richard Opalka (JIRA)

Remove deployers ordering workaround forAS 6.x series ----------------------------------------------------- Key: JBWS-2835 URL: https://jira.jboss.org/jira/browse/JBWS-2835 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-metro-3.2.2, jbossws-cxf-3.2.2, jbossws-native-3.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2809) Investigate why MemoryBufferRecorderTestCase is failing

by Richard Opalka (JIRA)

Investigate why MemoryBufferRecorderTestCase is failing ------------------------------------------------------- Key: JBWS-2809 URL: https://jira.jboss.org/jira/browse/JBWS-2809 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-3.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2009