anonymous wrote : "It is the deployer's responsibility not the application's, that is why resource-refs exist. | If you've followed the j2ee recommendations no refactoring should be required. "
Ok, fine, then leave it up to the application deployer. As it stands, it's not even an option to choose a local JMS server because it is GONE. anonymous wrote : You mean like server/default/deploy/jms | rather than server/all/deploy-hasingleton/jms Almost. I mean a server/all/deploy/jms that contains a local JMS server, with a way to get at it through HA. Basically, I want the exact same configuration that existed in 3.2.3. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843425#3843425 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843425 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
