On Tue, May 27, 2014 at 10:13 PM, [email protected] <[email protected]> wrote: > I have a couple of Questions: > > I have a standalone (legacy) application that creates a Spring Parent > Context which is where the CamelContext is created. Spring Batch is, also, > created in the Parent Context. What this application does is create a Child > Context for each of the Spring Batch Jobs when the Job executes. Then, when > a Job is completed, it tears down the Child Context. This inadvertently > tears down the CamelContext and stops all of the routes. > > Is there always one Instance of a Camel Context throughout ALL of the > Hierarchical Spring Contexts? > For instance, there would only be 1 Camel Context in the following scenario: > - Create Parent Context with Camel Context created > -- Create First Child Context > -- Create Second Child Context > > Is there a way to tell the CamelContext to NOT shutdown while there is a > Parent Context still around? >
I do not think so. As this can be complicated to get correct, (make sure it keep works for all the other users) I cannot see a good solution to this. You are welcome to look in camel-spring and debug and see in that spring event if there is anything of use to figure out a way to do what you want > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Context-shutdown-by-Spring-Child-Context-tp5751633.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
