Re: How can I avoid hard coding the remote queue name in @MessageDriven when using resource adapter

2017-05-03 Thread asdfg195
ot;true")}) public class MyNotificationMDB implements MessageListener { ... } This allows use to use the JNDI name of the queue defined in standalone.xml Queue.Notifications.Project -- View this message in context:

Re: How can I avoid hard coding the remote queue name in @MessageDriven when using resource adapter

2017-05-03 Thread Justin Bertram
To: users@activemq.apache.org Sent: Tuesday, May 2, 2017 4:41:09 PM Subject: Re: How can I avoid hard coding the remote queue name in @MessageDriven when using resource adapter That's more a question to the application server guys.. I would ask that question to wildfly. I believe there's

Re: How can I avoid hard coding the remote queue name in @MessageDriven when using resource adapter

2017-05-02 Thread Clebert Suconic
> > I am not a big fan of this solution since we will have many queues and > setting system properties for each will be a difficult maintenance problem. > Are there any alternative ways that will allow me to not hard code the > remote queue name into my MDB? > > > >

How can I avoid hard coding the remote queue name in @MessageDriven when using resource adapter

2017-05-02 Thread asdfg195
s message in context: http://activemq.2283324.n4.nabble.com/How-can-I-avoid-hard-coding-the-remote-queue-name-in-MessageDriven-when-using-resource-adapter-tp4725481.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.