[CAMEL-8000] Add global notion of CamelContextRegistry

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.14.0
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Thomas Diesler
• Created: 06/Nov/14 13:51
• Updated: 26/Nov/14 09:17
• Resolved: 18/Nov/14 11:54

Description

There are a number of issues with the Container API that make it unusable in WildFly

1. Concept of unsynchronised singleton
2. Call to 3rd party code with partially constructed objects
3. Unsynchronised access to a shared resource

Currently there are at least two components that compete for the Container singleton. The Camel Subsystem and Insight Camel.

I suspect that the Container API cannot be fixed in a compatible way.
Instead the notion of a CamelContextRegistry that fixes the issues with Container may need to get added.

Issue Links

• is related to: CAMEL-7968 Container has undefined concurrency behaviour
• is related to: CAMEL-7969 Container sees Context prematurely (with default name)
• is related to: CAMEL-7970 Container does not see the unregister event
• relates to: CAMEL-8059 Add CamelContext creation hook