servicemix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hrvoje Simic <hsi...@croz.net>
Subject Configuring components not to start
Date Sun, 05 Nov 2006 15:56:24 GMT

Is there any way to configure a specific component not to start when the
ServiceMx container is started? The component would be initialized and in
the state "stopped", and could be started at a later time using JMX or
through another component.

This is very useful in some cases if you want to control the component via a
JMX console. We have been using a custom "ignoreNextStart" property to make
component do nothing the first time start() is invoked (during container
startup), but this is not a very good solution. It appears that in
ServiceMix 3.0 the JMX console will not invoke start() on the component
already in state "started", so you have to stop() it first.

-- 
View this message in context: http://www.nabble.com/Configuring-components-not-to-start-tf2577935s12049.html#a7186350
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Mime
View raw message