In the distro there is a file call jms-ds.xml. This contains all the configuration for a *local* jms provider.
If you use the JCA resource adaptor at java:/JmsXA then you will be talking to the local JMS provider (via a resource adaptor). You can create another one of these files (or you can put in the same file - it doesn't matter) with all the information corresponding to your remote JMS provider. Make sure you give the tx-connection-factory a name different to your local one! Then when you use your java:/MyRemoteJMSXA or whatever you have called it, you will be talking to your remote provider. The above method is recommended if you want to take advantage of the transaction enlistment, security propagation features of the JCA adaptor. Alternatively you can just create your own InitialContext with a map of JNDI properties corresponding to the remote provider as per standard JNDI. But then you won't get automatic transaction enlistment, in EJBs for example. There are lots of wiki pages that cover this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074742#4074742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074742 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
