1. that's the way 2. no for the mentionned reasons. The way to solve it would likely be to write a remote EJB acting as a proxy and getting injected the factory and queue or equivalent.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-07-05 15:03 GMT+02:00 Dignesh <[email protected]>: > Thank you Romain. > > 1.I am using ejbd:// for JNDI look up to ejb's - The ejb's are deployed in > tomee. I have activated it by adding > openejb.service.manager.class = > org.apache.openejb.server.SimpleServiceManager > in system.properties file - No issues with this configuration. Please let > me know I am doing some thing wrong here. > > 2.Is there any other alternative apart from configuring connection > factories > in client as system property. > In short i dont want to have below two statements in my client program > System.setProperty("aConnectionFactory", > > "connectionfactory:org.apache.activemq.ActiveMQConnectionFactory:tcp://localhost:11616"); > System.setProperty("aQueue", > "queue:org.apache.activemq.command.ActiveMQQueue:LISTENER"); > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Remote-JNDI-look-up-to-ConnectionFactories-is-failing-tp4679228p4679232.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
