[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1014) Support injection of socket factory class name into AbstractInvoker

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno commented on JBREM-1014:
-----------------------------------------

Ron, that won't work either because the configuration map on the 
client side is empty as a result of EJB3 not passing down the wire the 
configuration map. Hence, no matter what you add to the map, it's 
unusable by the client..

If EJB3 had passed the configuration map down to the client, you 
wouldn't even have needed the SOCKET_FACTORY_CLASS_NAME
because createSocketFactory() in AbstractInvoker would treat 
SOCKET_FACTORY_NAME as class name.

The 2nd option is setting the socket factory class name via introspection 
by adding a AbstractInvoker.setSocketFactoryClassName(String socketFactoryClassName) 
to take a String but this is API addition. The reason I'm asking for this is 
because we can configure the client bind url like this:

sslsocket://${jboss.bind.address}:3853/?socketFactory=com.acme.security.TrustEveryoneSSLSocketFactory

However, this won't work because for PropertyEditors, there's not an 
equivalent AbstractInvoker.setSocketFactory(String socketFactory) , hence, 
we need something like AbstractInvoker.setSocketFactoryClassName(String socketFactoryClassName) 
and then configure the client bind url like this:

sslsocket://${jboss.bind.address}:3853/?socketFactoryClassName=com.acme.security.TrustEveryoneSSLSocketFactory

It's either that, or pass the Configuration object down the wire to EJB3 clients 
which would break if not coded properly.

> Support injection of socket factory class name into AbstractInvoker
> -------------------------------------------------------------------
>
>                 Key: JBREM-1014
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1014
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP8
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.2.2.SP9
>
>
> It is intended that org.jboss.remoting.AbstractInvoker can accept the class name of a SocketFactory, using the parameter org.jboss.remoting.Remoting.SOCKET_FACTORY_NAME (actual value "socketFactory").  Unfortunately, the parameter name "socketFactory" conflicts with the bean property of the same name.  In particular, the problem is that the method
>       public void setSocketFactory(SocketFactory socketFactory)
> in AbstractInvoker expects a SocketFactory instead of a String.

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