[
https://issues.apache.org/jira/browse/CAMEL-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212432#comment-14212432
]
Claus Ibsen commented on CAMEL-8000:
------------------------------------
The clear is needed as the registry is pre filled
Results :
Failed tests:
CamelContextRegistryTest.testContainerSet:57 expected:<2> but was:<107>
Though that smells the registry leaks during testing, and its likely better to
turn the registry off by default, and if ppl want to use it they need to enable
it explict.
I fear that it can lead to class loader leaks and whatnot for people in
environments where they depeploy apps and whatnot.
> Add global notion of CamelContextRegistry
> -----------------------------------------
>
> Key: CAMEL-8000
> URL: https://issues.apache.org/jira/browse/CAMEL-8000
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.14.0
> Reporter: Thomas Diesler
> Assignee: Claus Ibsen
> Fix For: 2.15.0
>
>
> 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.
> Instead the notion of a CamelContextRegistry that fixes the issues with
> Container may need to get added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
