On Mon, Oct 29, 2012 at 10:25 AM, Benjamin Graf <benjamin.g...@gmx.net> wrote: > Hi Claus, > > thanks so far. But does any method exists to avoid auto starting context > using Spring OSGi with bundles activated? >
No, but you can if possible just dont start the bundle itself. And then start the bundle to start Camel. The problem is that there is a chicken-egg situation. CamelContext need to be started so people can start it, using eg JMX etc. And for that the context needs to be started to enlist in JMX etc. > Benjamin > > -------- Original-Nachricht -------- >> Datum: Mon, 29 Oct 2012 09:33:49 +0100 >> Von: Claus Ibsen <claus.ib...@gmail.com> >> An: users@camel.apache.org >> Betreff: Re: Camel context autostartup > >> The autostartup options is for controlling if *routes* should be auto >> started or not. >> Not the actual CamelContext itself. >> >> The naming could have been better, but the option was first on <route> >> and then later inherited on <camelContext> to make a single switch. >> >> >> On Sat, Oct 27, 2012 at 4:57 PM, Benjamin Graf <benjamin.g...@gmx.net> >> wrote: >> > Hi, >> > >> > can anybody explain me why camel context state is set to started if >> autostartup >> > is set to false? This sound a bit odd to me. >> > >> > Best, >> > Benjamin >> > >> >> >> >> -- >> Claus Ibsen >> ----------------- >> Red Hat, Inc. >> FuseSource is now part of Red Hat >> Email: cib...@redhat.com >> Web: http://fusesource.com >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
