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, if you're running Camel as a standalone Java instance." Is there a technical reason why an application would only want 1 CamelContext per JVM? Meaning, does the CamelContext create a singleton classes that have a certain state which may be changed by a different CamelContext? If there isn't, could we get the documentation updated to be a little more accurate? -- View this message in context: http://camel.465427.n5.nabble.com/one-context-or-multiple-contexts-tp5754635p5755184.html Sent from the Camel - Users mailing list archive at Nabble.com.
