[ https://jira.jboss.org/jira/browse/JBREM-1121?page=com.atlassian.jira.plu... ] Ron Sigal commented on JBREM-1121: ---------------------------------- org.jboss.remoting.RemoteClientInvoker now uses the new constant org.jboss.remoting.Remoting.USE_ALL_SOCKET_FACTORY_PARAMS (actual value "useAllSocketFactoryParams") to determine whether it should pass just the configuration map or the combination of configuration map and InvokerLocator parameters to org.jboss.remoting.AbstractInvoker.createSocketFactory(). Note that the "combination of configuration map and InvokerLocator" is created by the AbstractInvoker constructor and is affected by the value, if any, of Remoting.CONFIG_OVERRIDES_LOCATOR (actual value "configOverridesLocator"), as described in JBREM-1124 "Invokers need option for configuration map parameters to override InvokerLocator parameters". Changes added to 2.x branch. Unit tests: * org.jboss.test.remoting.socketfactory.UseAllSocketFactoryParamsTestCase * also, added methods to org.jboss.test.remoting.socketfactory.SocketFactoryClassNameTestRoot, created for JBREM-1015 "CLONE [JBREM-1014] - Support injection of socket factory class name into AbstractInvoker", to verify that adding Remoting.USE_ALL_SOCKET_FACTORY_PARAMS doesn't interfere with the functionality introduced in JBREM-1015. Waiting for results in hudson. -- 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

[ https://jira.jboss.org/jira/browse/JBREM-1121?page=com.atlassian.jira.plu... ] Ron Sigal commented on JBREM-1121: ---------------------------------- Changes applied to 2.2 branch. -- 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

[ https://jira.jboss.org/jira/browse/JBREM-1121?page=com.atlassian.jira.plu... ] Ron Sigal closed JBREM-1121. ---------------------------- Resolution: Done Updated Remoting Guide on 2.2 and 2.x branches. -- 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

[ https://jira.jboss.org/jira/browse/JBREM-1121?page=com.atlassian.jira.plu... ] deckrider deckrider commented on JBREM-1121: -------------------------------------------- I see me earlier comment was incomplete. So I've upgraded to remoting 2.2.3 and added this configuration to jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/META-INF/jboss-service.xml: <mbean code="org.jboss.remoting.transport.Connector" name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"> <depends>jboss.aop:service=AspectDeployer</depends> <attribute name="InvokerLocator"><![CDATA[sslsocket://${jboss.bind.address}:3873/?org.jboss.remoting.Remoting.useAllSocketFactoryParams=true&org.jboss.remoting.serverAuthMode=false]]></attribute> <attribute name="Configuration"> <handlers> <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler> </handlers> </attribute> </mbean> However, it is not working. Can anyone help please? -- 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