We use a static XML configuration. And anyway, I don't like the persisted state solution, because there are components that should be manually started after the ESB crashes. I thought of a workaround using an ant task which only installs the component and doesn't start it, but that's kinda complicated.
Anyway, I've raised an Improvement on JIRA: http://issues.apache.org/activemq/browse/SM-737 [SM-737] New activation spec property: component is not to be started on container startup gnodet wrote: > > Do you use standard JBI components or a static xml configuration > file ? If you use JBI components and Service Assemblies, the state > of the components and service assemblies is persisted at shutdown > and restored at startup. > > But I guess adding an attribute on the activationSpec should > be easy do to. Please raise a JIRA and attach a patch if > you can :) > -- View this message in context: http://www.nabble.com/Configuring-components-not-to-start-tf2577935s12049.html#a7190435 Sent from the ServiceMix - User mailing list archive at Nabble.com.
