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 some point, to make the architecture more module at some point.
-- View this message in context: http://camel.465427.n5.nabble.com/Camel-Context-shutdown-by-Spring-Child-Context-tp5751633p5751662.html Sent from the Camel - Users mailing list archive at Nabble.com.
