[infinispan-issues] [JBoss JIRA] Updated: (ISPN-379) JGroupsChannelLookup should take in Properties created from props set on the transport

[ https://jira.jboss.org/jira/browse/ISPN-379?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-379: ------------------------------- Component/s: Configuration RPC Affects Version/s: 4.0.0.Final Description: The current JGroupsChannelLookup interface - http://docs.jboss.org/infinispan/4.1/apidocs/org/infinispan/remoting/tran... - does not have a mechanism to receive any configuration props. When configuring a transport, Infinispan allows arbitrary <properties /> to be set (see http://docs.jboss.org/infinispan/4.1/apidocs/config.html#ce_global_transport ). These should simply be passed in to JGroupsChannelLookup.getJGroupsChannel(). (was: The current JGroupsChannelLookup interface - http://docs.jboss.org/infinispan/4.1/apidocs/org/infinispan/remoting/tran... - does not have a mechanism to receive any configuration props. When configuring a transport, Infinispan allows arbitrary <properties /> to be set (see http://docs.jboss.org/infinispan/4.1/apidocs/config.html#ce_global_transport). These should simply be passed in to JGroupsChannelLookup.getJGroupsChannel().) -- 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