[CAMEL-7327] Improve Container.Instance API to deal with setting a Container after CamelContexts have been created. There is a big risk CamelContext's won't get managed right now

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.12.3
• Fix Version/s: 2.13.1, 2.14.0
• Component/s: camel-core, osgi
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: James Strachan
• Created: 25/Mar/14 13:10
• Updated: 28/Mar/14 10:30
• Resolved: 28/Mar/14 10:30

Description

In environments like OSGi startup ordering is kinda random. Right now CamelContexts's can startup and call

Container.Instance.manage(CamelContext)

https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/spi/Container.java#L64

before any Container has called Container.Instance.set(). These CamelContexts's will then not be managed.

A neater solution would be, if there is no container currently set:
https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/spi/Container.java#L66

then keep a track of the CamelContext objects in a Set<CamelContext> - until Container.Instance.unmanage() is called when they are stopped; then when Container.Instance.set(Container) is called; all the previously registered CamelContext's can be passed into the Container (and removed from the Set).