[
https://issues.apache.org/jira/browse/AXIS2-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469063
]
Matt Lovett commented on AXIS2-2020:
------------------------------------
The patch went in a few days ago:
http://svn.apache.org/viewvc?view=rev&revision=499521
> JAX-WS clients using sync-2-way and RM fail
> -------------------------------------------
>
> Key: AXIS2-2020
> URL: https://issues.apache.org/jira/browse/AXIS2-2020
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws, kernel
> Reporter: Matt Lovett
> Assigned To: Deepal Jayasinghe
> Attachments: opClient.patch, opClient2.patch
>
>
> Hi all,
> I have been doing some testing with jax-ws applications with Sandesha
> engaged, and I hit an issue with sync-2-way messaging. The axis ServiceClient
> and OutInOperationClient have some logic to force the invocation down the
> async path, which is what is needed in this case. (The addition of RM into
> the mix effectively makes the invocation async, even though we are using
> synchronous comms). Unfortunately, the jax-ws layer calls into the
> OutInOperationClient, and bypasses the logic in the ServiceClient. The same
> issue would apply to any other component that chooses to use the operation
> client directly.
> My suggested fix is to push some of the logic that is currently in the
> ServiceClient down into the operation client. I'll attach a patch soon, but
> the basic idea is to move the SyncCallBack class down.
> Thanks, Matt
--
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]
