[
https://issues.apache.org/jira/browse/AXIS2-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Lovett resolved AXIS2-1972.
--------------------------------
Resolution: Fixed
> Enable Sandesha to control reliable sync 2-way clients
> ------------------------------------------------------
>
> Key: AXIS2-1972
> URL: https://issues.apache.org/jira/browse/AXIS2-1972
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Reporter: Matt Lovett
> Assigned To: David Illsley
> Attachments: sync2WayAxis.patch
>
>
> As described in Sandesha2 JIRA
> https://issues.apache.org/jira/browse/SANDESHA2-64, we currently have a
> problem configuring clients that want to do sync 2-way messaging using WS-RM.
> It would be nice to allow the Sandesha module to take care of the
> configuration for them, so that the client code doesn't need to change when
> we engage the Sandesha module.
> The solution I am proposing is to add a new configuration constant, which the
> operation and service clients can check for. In the special case where are
> are doing sync 2-way, and this option is present, then we setup a callback
> object. The Sandesha module then drives the response message back through the
> axis engine, and triggers the callback, which can then return to the
> application.
> This code is very similar to, but not quite the same as USE_CUSTOM_LISTENER.
> I think that option was introduced for Sandesha too, but doesn't seem to be
> used. Once we add in the new option that I need I'd be happy to supply a
> second patch to remove or deprecate that option, if people would like me to.
> I'll attach a patch that implements the Axis2 half of the changes I need.
--
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]
