JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in
AxisInvocationController.
---------------------------------------------------------------------------------------------------
Key: AXIS2-909
URL: http://issues.apache.org/jira/browse/AXIS2-909
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Reporter: Nick Gallardo
I've implemented the invokeOneWay and invokeAsync-callback methods in the
AxisInvocationController. The sync had already been implemented in a previous
defect.
Also, I've updated the BaseDispatch to use this rather than the original
AxisController. This brings us much closer to removing the AxisController API
in favor of the AxisInvocationController. The changes to the async impl
requires updates to the callbacks that are used. Specifically, the
AsyncResponse/AsyncResponseProcessor have been renamed to be a little more
intuitive.
The AsyncListener is the task that will wait for the async response to come
back. This will be wrapped in an AsyncListenerWrapper that controls the
starting and stopping. This AsyncListenerWrapper is what will be used by the
JAX-WS client to determine if a response is available or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
