[
https://jira.jboss.org/jira/browse/JBREM-1124?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1124:
----------------------------------
AbstractInvoker now uses org.jboss.remoting.Remoting.CONFIG_OVERRIDES_LOCATOR (actual
value "configOverridesLocator") to determine its behavior. It looks for a value
in the configuration map and then looks in the InvokerLocator. If the last value found is
"true", then AbstractInvoker gives priority to parameter values found in the
configuration map.
Unit tests: org.jboss.test.remoting.configuration.ConfigOverridesLocatorTestCase .
Tests are passing in hudson.
Need to update Remoting Guide.
Invokers need optiion for configuration map parameters to override
InvokerLocator parameters
--------------------------------------------------------------------------------------------
Key: JBREM-1124
URL:
https://jira.jboss.org/jira/browse/JBREM-1124
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.2 (Flounder)
org.jboss.remoting.AbstractInvoker, the parent of all client and socket invokers,
constructs a map of parameters by taking an InvokerLocator and an optional configuration
map. Currently, it adds the elements of the configuration map, if it exists, and then
adds the InvokerLocator parameters, if any, It follows that if a parameter is in both,
then the value in the InvokerLocator takes precedence.
There should be an option for the values in the configuration map to take precedence.
--
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