In doing research about implementing multiple CamelContexts within a single
JVM, I have seen the information on this page pop up in several different
places.
http://camel.apache.org/why-use-multiple-camelcontext.html
"In general, you don't tend to want multiple camel contexts in your
application,
After much digging around, I agree this can be tricky to get right. Since I
am working with a legacy monolithic application, the only solution I see is
to create a separate Application Context for just Camel and the Messaging.
This will keep it separate from the other Contexts and allow us, at so
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
