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? -- 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.
