July 2009 - jbossws-issues - Jboss List Archives

[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

15 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JBWS-2647) Reference to jboss-xml-binding.jar in ws scripts should be changed to match name in repository.

by Paul Gier (JIRA)

Reference to jboss-xml-binding.jar in ws scripts should be changed to match name in repository. ----------------------------------------------------------------------------------------------- Key: JBWS-2647 URL: https://jira.jboss.org/jira/browse/JBWS-2647 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Gier Currently the webservices startup scripts refer to the jar "jboss-xml-binding.jar". These should be changed to match the name of the jar in the repository "jbossxb.jar" -- 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

15 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2654) NumberFormatException when using StubExt.PROPERTY_CLIENT_TIMEOUT

by Pras P (JIRA)

NumberFormatException when using StubExt.PROPERTY_CLIENT_TIMEOUT ---------------------------------------------------------------- Key: JBWS-2654 URL: https://jira.jboss.org/jira/browse/JBWS-2654 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.5 Environment: RHEL Reporter: Pras P This bug is similar to https://jira.jboss.org/jira/browse/JBWS-1410 however, it still exists in 3.0.5 when used with soapAddress which looks like http://10.10.10.204:8557 and a timeout is set using StubExt.PROPERTY_CLIENT_TIMEOUT Looks like there is a parsing error where the port is also carried over (8557 in the exception below is a port) 2009-05-20 21:50:02,181 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception java.lang.NumberFormatException: For input string: "8557?timeout=60000" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:456) at java.lang.Integer.parseInt(Integer.java:497) at org.jboss.remoting.InvokerLocator.<init>(InvokerLocator.java:191) at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:206) at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) The exception does not occur when a soapAddress is of the following format http://10.10.10.204:8557/adm/admWS -- 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

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2651) ClassCast Exception in case of malformed webservice response

by Gandulf Kohlweiss (JIRA)

ClassCast Exception in case of malformed webservice response ------------------------------------------------------------ Key: JBWS-2651 URL: https://jira.jboss.org/jira/browse/JBWS-2651 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.1 Environment: Windows XP JDK 1.6 JBoss 4.2.3 GA JBossWs 3.1.1 Reporter: Gandulf Kohlweiss At the moment jbossws throws a ClassCast Exception in case of an illegal webservice response (missing closing tag, etc...) : [code] Caused by: javax.xml.ws.WebServiceException: java.lang.ClassCastException: org.jboss.ws.core.soap.Te xtImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementI mpl at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) at $Proxy311.bookOrders(Unknown Source) at com.skidata.dta.server.co.v3_0.classic.impl.BookOrdersHelper.invoke(BookOrdersHelper.java :46) ... 12 more Caused by: 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:894) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) ... 16 more [/code] It would be helpful to get the actual Parse Excpetion from the xml parser instead of this classcastexcpetion. Digging through the code i found out that this might occur because the MessageFectory to parse the response is initialized with ignoreParseErrors = true. e.g in the SOAPMessageUnMarshallerHTTP at line 82 (source .3.1.1.GA) [code] MimeHeaders mimeHeaders = getMimeHeaders(metadata); soapMsg = getMessageFactory().createMessage(mimeHeaders, inputStream, true); [/code] -- 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

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2692) Define client/server security policy for JBWS testsuite and run it under a security manager

by Alessio Soldano (JIRA)

Define client/server security policy for JBWS testsuite and run it under a security manager ------------------------------------------------------------------------------------------- Key: JBWS-2692 URL: https://jira.jboss.org/jira/browse/JBWS-2692 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 We should start from the server.policy and client.policy that comes in the AS testsuite (see testsuite/src/resources/securitymgr). Those policies most probably require additions for some trusted libraries used by jbossws-native and apache cxf. The goal is being able to run the whole testsuite under a security manager. -- 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

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-1800) Trying to monitor the JVM using -Dcom.sun.management.jmxremote prevents the jbossws 2.0.1 from coming up

by Raju Koganty (JIRA)

Trying to monitor the JVM using -Dcom.sun.management.jmxremote prevents the jbossws 2.0.1 from coming up -------------------------------------------------------------------------------------------------------- Key: JBWS-1800 URL: http://jira.jboss.com/jira/browse/JBWS-1800 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1 Environment: JBossWS 2.0.1 on JBoss 4.0.5 with JDK 1.6 Reporter: Raju Koganty Having -Dcom.sun.management.jmxremote in the startup args to monitor the JVM causes this exception during startup and jbossws 2.0.1 doesn't come up : And here is the exception : java.lang.NullPointerException at org.jboss.wsf.stack.jbws.WSDLFilePublisher.getPublishLocation(WSDLFilePublisher.java:303) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:103) at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) at org.jboss.wsf.container.jboss40.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss40.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.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 $Proxy29.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.GeneratedMethodAccessor20.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 $Proxy8.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.GeneratedMethodAccessor3.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:302) 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:490) at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 1 month

6
7
0 / 0

[JBoss JIRA] Created: (JBWS-2700) Many DOM API methods not implemented

by Gang Yang (JIRA)

Many DOM API methods not implemented ------------------------------------ Key: JBWS-2700 URL: https://jira.jboss.org/jira/browse/JBWS-2700 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Gang Yang Priority: Critical Many DOM API methods, such as setIdAttribute*(), adoptNode(), getTextContent(), etc. were not implemented by SOAPPart and/or SOAPElement implementation. This causes incompatibility with many other 3rd party packages, such as OpenSAML, WSS4J. This also make writing SOAP message processing software difficult for JBossWS. -- 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

15 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2660) Investigate enabling JMS transport with CXF stack

by Alessio Soldano (JIRA)

Investigate enabling JMS transport with CXF stack ------------------------------------------------- Key: JBWS-2660 URL: https://jira.jboss.org/jira/browse/JBWS-2660 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano -- 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

15 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2479) @XmlJavaTypeAdapter on SEI causes exception

by Alessio Soldano (JIRA)

@XmlJavaTypeAdapter on SEI causes exception ------------------------------------------- Key: JBWS-2479 URL: https://jira.jboss.org/jira/browse/JBWS-2479 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano When annotation a method/parameter in the SEI with @XmlJavaTypeAdapter, we get an exception from APT. See: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=557 -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2674) Implement javax.xml.ws.Endpoint

by Richard Opalka (JIRA)

Implement javax.xml.ws.Endpoint ------------------------------- Key: JBWS-2674 URL: https://jira.jboss.org/jira/browse/JBWS-2674 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.1 We do have implementation of this Endpoint API, but it is fundamentally wrong. I'd say the Endpoint as specified in the JAX-WS spec was misunderstood by the author of current Endpoint implementation. The Endpoint static methods are intended to be used on client side and have nothing to do with the server side (this is our current implementation). Adrian is right about it too. We shouldn't use main deployer in jbossws AS IL, see: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4059193#4059205 We're using it because of our current Endpoint impl. But Endpoint impl as specified in JAX-WS spec has nothing to do with endpoint publishing in server runtime. Thus current Endpoint implementation needs complete rewrite to be usable on client side only in single JVM without Server incorporated. I'm removing the old endpoint implementation from server integration layer for now. This removal represents no problem for us at the moment, because endpoint publish() method sets are now excluded in TCK5 and it passes even without that Endpoint impl. However this needs to be fixed in the future, because JAX-WS spec requires it (although this is not tested in the TCK now). -- 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

15 years, 2 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2009