[
https://jira.jboss.org/jira/browse/JBREM-1082?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1082:
----------------------------------
ConnectionValidator looks for the parameter Client.USE_ALL_PARAMS (actual value
"useAllParams") in the InvokerLocator, the Client's configuration map, and
in the metadata map passed to Client.addConnectionListener(), in that order. If the
result of that search finds the parameter "useAllParams" set to
"true", then ConnectionValidator will look for parameter values in the
InvokerLocator before looking, as before, in the Client's configuration map and the
metadata map.
Unit tests:
org.jboss.test.remoting.connection.params.ConnectionValidatorConfigurationTestCase
Will wait for the results from Hudson.
Allow ConnectionValidator to access InvokerLocator parameters
-------------------------------------------------------------
Key: JBREM-1082
URL:
https://jira.jboss.org/jira/browse/JBREM-1082
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.addConnectionListener() creates an
org.jboss.remoting.ConnectionValidator, it passes in a reference to itself and the
ConnectionValidator accesses the Client's configuration map. However, the
Client's configuration map doesn't include (without some action on the part of the
calling application) the InvokerLocator parameters. It follows that parameters configured
on the server side (e.g., in a *-service.xml or *-beans.xml file in the context of the
Application Server) don't get passed to the ConnectionValidator.
--
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