[
https://issues.apache.org/jira/browse/CAMEL-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201850#comment-14201850
]
ASF GitHub Bot commented on CAMEL-8000:
---------------------------------------
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/322
[CAMEL-8000] Add global notion of CamelContextRegistry
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel bug8000
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/322.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #322
----
commit 6f428a8390910786de64abd4771604a213171842
Author: Thomas Diesler <thomas.dies...@jboss.com>
Date: 2014-11-07T09:48:15Z
[CAMEL-8000] Add global notion of CamelContextRegistry
----
> Add global notion of CamelContextRegistry
> -----------------------------------------
>
> Key: CAMEL-8000
> URL: https://issues.apache.org/jira/browse/CAMEL-8000
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.14.0
> Reporter: Thomas Diesler
> 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)
