For a start, ActiveMQ might not even be on the same machine if OpenEJB is configured to use a remote ActiveMQ server. The fact that we start an embedded broker is purely to provide an out of the box solution. You may even choose to use a completely different MQ.
You and your application are responsible for configuring and exposing what you want, not OpenEJB (It would be very wrong if OpenEJB were to do this automatically). You have several options. 1. Keep the MQ hidden from clients and expose messaging methods on your own custom bean/s. ... myBean.sendMessage(myQueueName, myMessage); ... final String msg = myBean.getMessage(myQueueName); 2. Expose the MQ properties, also through your own custom bean/s and connect to Act. ... final String jmsHost = myBean.getJmsHost(); ... Connect to the MQ directly and use JMS... 3. Something completely different. Just remember, ActiveMQ is a *fully fledged server application*. If you intend to expose any kind of remote connection to it then you are responsible for ensuring that security is properly configured. http://activemq.apache.org/security.html Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/help-on-activemq-with-openejb-tp4660758p4660885.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
