Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 26 Nov 2014 09:18:12 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12753401.1415281876000.24905.1416993492565@Atlassian.JIRA>
In-Reply-To: <JIRA.12753401.1415281876000@Atlassian.JIRA>
References: <JIRA.12753401.1415281876000@Atlassian.JIRA>
 <JIRA.12753401.1415281876660@arcas>
Subject: [jira] [Commented] (CAMEL-8000) Add global notion of
 CamelContextRegistry
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225942#comment-14225942 ] 

ASF GitHub Bot commented on CAMEL-8000:
---------------------------------------

Github user tdiesler closed the pull request at:

    https://github.com/apache/camel/pull/322


> 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
>
> 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)