Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
There are a number of issues with the Container API that make it unusable in WildFly
- Concept of unsynchronised singleton
- Call to 3rd party code with partially constructed objects
- 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.
Attachments
Issue Links
- is related to
-
CAMEL-8000 Add global notion of CamelContextRegistry
- Resolved