[jboss-jira] [JBoss JIRA] Commented: (JBAS-4456) Replace JRMPProxyService with a remoting based bean.

[ https://jira.jboss.org/jira/browse/JBAS-4456?page=com.atlassian.jira.plug... ] Ron Sigal commented on JBAS-4456: --------------------------------- The class org.jboss.aspects.remoting.RemotingProxyFactory, which functionally replaces org.jboss.invocation.jrmp.server.JRMPProxyFactory, now exists in the jboss-aspects project. I've announced its existence on the development mailing list, with javadoc attached. I don't see how to incorporate the incoming client address into a proxy. However, Remoting 2.4 supports InvokerLocators with multiple connect addresses. For example, a Connector configured with <mbean code="org.jboss.remoting.transport.Connector" name="jboss.remoting:service=Connector,transport=Socket" display-name="Socket transport Connector"> <attribute name="Configuration"> <config> <invoker transport="socket"> <attribute name="homes"> <home>10.32.4.2:6500</home> <home>192.168.4.2:6501</home> </attribute> <attribute name="connecthomes"> <connecthome>10.32.42.2:7500</connecthome> <connecthome>192.168.42.2:7501</connecthome> </attribute> </invoker> <handlers> ... </handlers> </config> </attribute> </mbean> will generate an InvokerLocator with the connect addresses 10.32.42.2:7500 and 192.168.42.2:7501. A client invoker will try the connect addresses until it finds one that works. -- 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