Hi I dont think you can do that, as we listen on ContextRefreshedEvent from spring before we start Camel.
We introduce a shutdownEager in CAMEL-7156 for camel-spring. We could consider a startEager option as well, so we start CamelContext sooner. Feel free to log a JIRA ticket http://camel.apache.org/support On Thu, Jun 26, 2014 at 8:59 PM, Jeff Bischoff <jbisch...@wdtablesystems.com> wrote: > When I try this, I see the "myCamel" bean instantiated (it has been passed > as a parameter to another bean) but it is not started at the time "foo" is > instantiated. If I use a breakpoint at this spot and take a look in > jconsole, I see that the Camel MBeans have not been registered yet. > > Later in the log (long after "foo" is initialized), I see the following in > the log: > > jvm 1 | 14:37:10,017 INFO [/wdts.table][SpringCamelContext] > (pool-6-thread-1) Apache Camel 2.13.1 (CamelContext: myCamel) is starting > > This seems to be the key line in the logs that shows things are really > starting... > > How do I trigger that earlier? > > Thank you, > > Jeff > > On 6/26/14 10:59 AM, "Claus Ibsen" <claus.ib...@gmail.com> wrote: > >>You set the others beans to have depends-on Camel. >> >><bean id="foo" depends-on="myCamel" ... >> >> ... >> >><camelContext id="myCamel" ... >> >> >>On Thu, Jun 26, 2014 at 4:52 PM, Jeff Bischoff >><jbisch...@wdtablesystems.com> wrote: >>> I'm having a problem using the Camel Spring DSL. Starting the routes >>>seems to be the very last thing that is done during Spring >>>initialization. >>> >>> How do I trigger Spring to fully initialize camel and all the camel >>>routes earlier in the Spring initialization process (i.e. before a >>>particular other bean is initialized)? >>> >>> >>> >>> Thanks, >>> >>> Jeff >>> ________________________________ >>> >>> Please take note: This email, including attachments, contains >>>information which may be confidential or legally privileged and is only >>>for the use of the individual or entity to whom it is properly >>>addressed. Any unauthorized review, use, disclosure, copying, or >>>distribution is prohibited. If you have reason to believe that you have >>>received this communication in error, or that it may be misaddressed or >>>not intended for you, please destroy it and notify the sender >>>immediately. Thank you. >> >> >> >>-- >>Claus Ibsen >>----------------- >>Red Hat, Inc. >>Email: cib...@redhat.com >>Twitter: davsclaus >>Blog: http://davsclaus.com >>Author of Camel in Action: http://www.manning.com/ibsen >>hawtio: http://hawt.io/ >>fabric8: http://fabric8.io/ > > ________________________________ > > Please take note: This email, including attachments, contains information > which may be confidential or legally privileged and is only for the use of > the individual or entity to whom it is properly addressed. Any unauthorized > review, use, disclosure, copying, or distribution is prohibited. If you have > reason to believe that you have received this communication in error, or that > it may be misaddressed or not intended for you, please destroy it and notify > the sender immediately. Thank you. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
