[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1082) Allow ConnectionValidator to access InvokerLocator parameters

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBREM-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal closed JBREM-1082.
----------------------------

    Resolution: Done


> Allow ConnectionValidator to access InvokerLocator parameters
> -------------------------------------------------------------
>
>                 Key: JBREM-1082
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1082
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      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.1 (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