[jbossws-issues] [JBoss JIRA] Reopened: (JBWS-2010) Select the right operation metadata when using Dispatch
[ http://jira.jboss.com/jira/browse/JBWS-2010?page=all ]
Richard Opalka reopened JBWS-2010:
----------------------------------
The provided fix is unacceptable. It breaks at least the following TCK 5 jaxws tests:
com/sun/ts/tests/jaxws/api/javax_xml_ws/Dispatch/Client.java#invokeAsyncHandlerTestSOAPMessage_from_wsappclient
com/sun/ts/tests/jaxws/api/javax_xml_ws/Dispatch/Client.java#invokeAsyncHandlerTestSOAPMessage_from_wsejb
com/sun/ts/tests/jaxws/api/javax_xml_ws/Dispatch/Client.java#invokeAsyncHandlerTestSOAPMessage_from_wsservlet
com/sun/ts/tests/jaxws/api/javax_xml_ws/Dispatch/Client.java#invokeAsyncTestSOAPMessage_from_wsappclient
com/sun/ts/tests/jaxws/api/javax_xml_ws/Dispatch/Client.java#invokeAsyncTestSOAPMessage_from_wsejb
com/sun/ts/tests/jaxws/api/javax_xml_ws/Dispatch/Client.java#invokeAsyncTestSOAPMessage_from_wsservlet
I rolled back the change in SOAPMessageDispatcher.java. There was a problem with Xerces
and multiple threads.
Select the right operation metadata when using Dispatch
-------------------------------------------------------
Key: JBWS-2010
URL: http://jira.jboss.com/jira/browse/JBWS-2010
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: jbossws-native-2.0.3
Reporter: Alessio Soldano
Assigned To: Alessio Soldano
Fix For: jbossws-native-2.0.4
Inspite of the Common/ClientImpl deriving the operation metadata from the invoked method,
the DispatchImpl doesn't even try to find out the operation metadata corresponding to
the message that is going to be sent. For instance this may be a potential issues when
using ws-security with custom target configuration.
--
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