Sorry but I have never even looked at that.
If it uses tomcat under that cover then you could probably use the same technique that I have mentioned here but again I do not know if that will work. If you have any experience with this app server you should see if there is a server.xml file that includes the listerner element. --Claudio >________________________________ > From: Daoud Abdelmonem Faleh <abdelmonem.fa...@gmail.com> >To: users@activemq.apache.org; Claudio Corsi <clco...@yahoo.com> >Sent: Monday, December 5, 2011 9:50 AM >Subject: Re: Multiple war in Tomcat 7 using a shared embedded ActiveMQ > >What about Apache TomEE? http://openejb.apache.org/apache-tomee.html > >On Mon, Dec 5, 2011 at 3:46 AM, Claudio Corsi <clco...@yahoo.com> wrote: >> Hi Dysan, >> >> I am not a tomcat expert but just looking at the server.xml file. There is >> the concept of a listener that you might want to consider as a way to >> start/stop the activemq broker. >> >> Here is a pointer to the javadoc. >> >> http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/LifecycleListener.html >> >> It receives a lifecycleevent instance that you can use to determine in which >> cycle the tomcat server is currently processing. >> >> >> Looking at the javadoc you should be able to determine which lifecycle event >> you should start the broker on and which cycle event you should shutdown the >> server. >> >> You could then define a mechanism to determine which connection information >> you should use to connect to the broker. >> >> This is just part of the general v7 javadoc located at: >> >> http://tomcat.apache.org/tomcat-7.0-doc/api/index.html >> >> >> Hope this helps, >> >> --Claudio >> >> >> >>>________________________________ >>> From: Dysan <sba...@hotmail.fr> >>>To: users@activemq.apache.org >>>Sent: Thursday, December 1, 2011 10:25 AM >>>Subject: Multiple war in Tomcat 7 using a shared embedded ActiveMQ >>> >>>Hi, >>> >>>I'm working on a project where several war inside a tomcat 7 have to >>>communicate with a single embedded activeMQ (5.5.1) broker inside the same >>>Tomcat. >>> >>>I'm wondering what was the best practice to manage this and how to start and >>>stop the broker properly. >>> >>>Actually i try tu use a global JNDI entry in server.xml and in each war get >>>my activemq connection with a lookup. The first connection to the broker >>>implicitly starts it. But with this method I run into various problems like >>>instance already existing or locks in data store. >>> >>>Should I use instead an additional war which uses a BrokerFactory to start >>>the broker explicitly ? In this case how to make sure that this war executes >>>first in Tomcat ? And how do I stop my broker and where ? >>> >>>Thanks for the help. >>> >>> >>>-- >>>View this message in context: >>>http://activemq.2283324.n4.nabble.com/Multiple-war-in-Tomcat-7-using-a-shared-embedded-ActiveMQ-tp4128926p4128926.html >>>Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>> >>> >>> > > >
