Running embedded is usually only done as an optimization, a deployment
requirement, or because you want to support a dynamic configuration of
activemq and you want your app to be able change the activemq
configuration on the fly.


On 8/2/06, javaxmlsoapdev <[EMAIL PROTECTED]> wrote:

I am just starting to use ActiveMQ 4.x latest with Spring 2.0. Since I am new
to ActiveMQ, wanted to understand pros and cons of using ActiveMQ as
embedded in Spring and running ActiveMQ standalone. Would it be more easier
to manage, adminster ActiveMQ activities, if it's configured outside spring
(not embedded)? What are the pluses of using it embedded in Spring.

Thanks,
--
View this message in context: 
http://www.nabble.com/Embedded-ActiveMQ-vs.-running-it-standalone-tf2040710.html#a5616853
Sent from the ActiveMQ - User forum at Nabble.com.




--
Regards,
Hiram

Blog: http://hiramchirino.com

Reply via email to