[jboss-jira] [JBoss JIRA] Commented: (JBREM-1084) Allow CallbackPoller to access Client and InvokerLocator parameters
[
https://jira.jboss.org/jira/browse/JBREM-1084?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1084:
----------------------------------
the value of org.jboss.remoting.Client.USE_ALL_PARAMS (actual value
"useAllParams") is checked, successively, in the InvokerLocator, the
Client's configuration map, and the metadata map passed to Client.addListener(). If
the first instance found is set to "true", then these three sources will be
checked, successively, for all other parameters used by CallbackPoller. Otherwise, only
the metadata map will be used, which is the original, and default, behavior.
Unit test: org.jboss.test.remoting.callback.params.UseAllParamsTestCase.
Will wait for hudson results.
Allow CallbackPoller to access Client and InvokerLocator parameters
-------------------------------------------------------------------
Key: JBREM-1084
URL: https://jira.jboss.org/jira/browse/JBREM-1084
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.0.SP3 (Flounder), 2.2.2.SP12
When org.jboss.remoting.Client.addListener() creates an
org.jboss.remoting.callback.CallbackPoller, it passes in a reference to itself and a
metadata map. Currently, the CallbackPoller accesses parameters only in the metadata map,
which means that the Client's configuration map and InvokerLocator parameters (which
might be configured declaratively on the server side) are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira