]
Alessio Soldano updated JBWS-2288:
----------------------------------
Fix Version/s: jbossws-native-3.0.6
Assignee: Alessio Soldano
Exception handling issue in org.jboss.ws.core.CommonClient.
-----------------------------------------------------------
Key: JBWS-2288
URL:
https://jira.jboss.org/jira/browse/JBWS-2288
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.3
Environment: Shown running JBossAS 4.2.2 & 4.2.3, JBossWS 3.0.1 & 3.0.3
on windows XP, JVM 1.5.0_15
Reporter: aodhan hoffman
Assignee: Alessio Soldano
Fix For: jbossws-native-3.0.6
In troubleshooting a problem another user, PeterJ, found what looks like a coding error
at line 404 in org.jboss.ws.core.CommonClient.invoke(). Exception is caught but details
are not logged before another method is called which in turn causes another exception. See
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141051
I tried using JBossWS 3.x stand alone, stock downloads of JBossAS 4.2.x and JBossAS 4.2.x
updated to JBossWS 3.0.1, 3.0.2, & 3.0.3. All versions of JBossWS 3.0.x appear to
contain this code segment.
// Stacktrace
Exception in thread "main" javax.xml.ws.WebServiceException:
java.lang.IllegalStateException: Cannot find property: java
x.xml.ws.handler.message.outbound
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 $Proxy19.update(Unknown Source)
at com.boeing.nmt.nls.mv4client.MV4Client.disableTag(MV4Client.java:308)
at com.boeing.nmt.nls.test.AssetTest.main(AssetTest.java:25)
Caused by: java.lang.IllegalStateException: Cannot find property:
javax.xml.ws.handler.message.outbound
at
org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.processPivot(MessageContextJAXWS.java:109)
at org.jboss.ws.core.jaxws.client.ClientImpl.processPivot(ClientImpl.java:363)
at org.jboss.ws.core.CommonClient.processPivotInternal(CommonClient.java:476)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:404)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
// Lines 401-420 of CommonClient.java
//
http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk/modules/core/sr...
catch (Exception ex)
{
// Reverse the message direction
processPivotInternal(msgContext, direction); // <-- line 404, where the
later exception gets thrown
if (faultType[2] != null)
callFaultHandlerChain(portName, faultType[2], ex);
if (faultType[1] != null)
callFaultHandlerChain(portName, faultType[1], ex);
if (faultType[0] != null)
callFaultHandlerChain(portName, faultType[0], ex);
throw ex;
}
finally
{
closeHandlerChain(portName, handlerType[2]);
closeHandlerChain(portName, handlerType[1]);
closeHandlerChain(portName, handlerType[0]);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: