[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1121) Client SocketFactory should be configurable by InvokerLocator

deckrider deckrider (JIRA) jira-events at lists.jboss.org
Wed Jul 1 23:56:51 EDT 2009


    [ https://jira.jboss.org/jira/browse/JBREM-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12474528#action_12474528 ] 

deckrider deckrider commented on JBREM-1121:
--------------------------------------------

I'm trying to understand how this new mechanism works.  It seems that adding org.jboss.remoting.serverAuthMode=false" to the EJB3 InvokerLocator.

Before remoting 2.2.3 I was using socketFactoryClassName=some.package.MySocketFactory as per http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153111 but replacing that with serverAuthMode=false isn't working.

I also tried useAllParams=true (as per the docs) but that didn't seem to help either.  And I'm not sure what do do about configOverridesLocator or whether thats having any effect.

> Client SocketFactory should be configurable by InvokerLocator
> -------------------------------------------------------------
>
>                 Key: JBREM-1121
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1121
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP11, 2.5.1 (Flounder)
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.2.3, 2.5.2 (Flounder)
>
>
> org.jboss.remoting.RemoteClientInvoker, which creates the client invoker's SocketFactory, uses only the parameters passed in the configuration map (except for looking in the InvokerLocator for org.jboss.remoting.SOCKET_FACTORY_CLASS_NAME (actual value "socketFactoryClassName"), which was introduced in JBREM-1014 "Support injection of socket factory class name into AbstractInvoker").  There should be a configurable option to use all parameters from the InvokerLocator.

-- 
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

        



More information about the jboss-remoting-issues mailing list