Simplify configuration of sync-2-way apps
-----------------------------------------
Key: SANDESHA2-64
URL: https://issues.apache.org/jira/browse/SANDESHA2-64
Project: Apache Sandesha2
Issue Type: Improvement
Reporter: Matt Lovett
The AnonymousEcho tests set up a sync 2-way exchange, and rely on the
PollingManager & MakeConnection message to get the messages back to the client.
Part of the client options include setting the following:
// Put in enough config to convince Axis that this is async,
without setting up
// new WS-Adressing replyTo etc.
clientOptions.setUseSeparateListener(true);
clientOptions.setProperty(Constants.Configuration.USE_CUSTOM_LISTENER,Boolean.TRUE);
Unfortunately this code is not appropriate when RM is not engaged, or when we
are sending an unreliable message, so the users code needs to change for these
cases. It would be much better to keep this config in Sandesha & Axis, so that
the users code stays the same.
I propose adding a new config option to Axis (rather similar to the existing
USE_CUSTOM_LISTENER), and applying the option to the ConfgurationContext when
the Sandesha module is engaged.
I'll attach the Sandesha half of the changes here, and open an Axis2 Jira for
the other half.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://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]
