On 3/7/07, Javier Leyba <[EMAIL PROTECTED]> wrote:
Hi
I've a JBoss service that starts my ActiveMQ brokers and it run's ok.
Now, I'm trying to deploy another application that is an axis server
deployed as a weapp to offer web services that will use activemq.
As JBoss services load classes before my webapp, my webapp could use
the classes loaded by the .sar. This was fantastic till today where I
tried to integrate my webapp with Spring... I received a lot of errors
calling a Spring webContextListener and discovered that errors were
produced because ActiveMQ comes with the whole Spring package and as
its loaded by the sar, my webapp thinks the app context was loaded...
So, I've two solutions:
1 - Try to know which Spring jars needs activemq to avoid the load of
spring-web in my sar.
2 - Try to isolated the webapp spring-web class loading to the whole war.
I found the first one more clean and easy so I wonder if somebody
could tell me wich Spring jars are needed by ActiveMQ.
The Spring jars are not mandatory, you can use ActiveMQ just fine
without it. Currently main use of Spring is along with xbean to deal
with the XML configuration. If you prefer you could just use Java code
to initialise your broker...
http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html
Though without having class loader isolation, am sure you'll hit your
head on other jar-dependency issues sooner or later so having solution
2 in your locker is highly recommended.
--
James
-------
http://radio.weblogs.com/0112098/
