[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1890) Recovery configuration in a cluster is too burdensome

[ https://issues.jboss.org/browse/JBMESSAGING-1890?page=com.atlassian.jira.... ] Justin Bertram commented on JBMESSAGING-1890: --------------------------------------------- Why not use a configuration like this: <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=JMSProviderRemote"> <attribute name="ProviderName">ClusteredRecoveryJMSProvider</attribute> <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> <attribute name="FactoryRef">java:/ClusteredXAConnectionFactory</attribute> <attribute name="QueueFactoryRef">java:/ClusteredXAConnectionFactory</attribute> <attribute name="TopicFactoryRef">java:/ClusteredXAConnectionFactory</attribute> <attribute name="Properties"> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=${jboss.bind.address}:1099 </attribute> </mbean> Since the local ClusteredXAConnectionFactory is part of cluster its stub should have all the necessary information to contact all the other nodes in the cluster, right? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira