JAX-WS Async Response.get() should cache the response object
------------------------------------------------------------
Key: AXIS2-2046
URL: https://issues.apache.org/jira/browse/AXIS2-2046
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Rich Scheuerle
Assigned To: Rich Scheuerle
The JAX-WS engine implements a Response<T> object for asynchronous clients.
A user invokes the get() method on the Response to obtain the returned business
object.
If the user invokes get() a second time, the JAX-WS tries to reparse the
messag, which causes a failure because the message has been consumed.
Instead, the first get() should cache the business object and the second get()
should simply return the cached object.
I am working on a small patch to fix this processing. The patch will include
an updated ParallelAsync test.
scheu
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
