[
https://jira.jboss.org/jira/browse/JBREM-1121?page=com.atlassian.jira.plu...
]
deckrider deckrider commented on JBREM-1121:
--------------------------------------------
Never mind, the following works:
<attribute
name="InvokerLocator"><![CDATA[sslsocket://${jboss.bind.address}:3873/?useAllSocketFactoryParams=true&org.jboss.remoting.serverAuthMode=false]]></attribute>
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