You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Thomas Diesler (JIRA)" <ji...@apache.org> on 2014/11/10 14:57:34 UTC
[jira] [Comment Edited] (CAMEL-8000) Add global notion of
CamelContextRegistry
[ https://issues.apache.org/jira/browse/CAMEL-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204794#comment-14204794 ]
Thomas Diesler edited comment on CAMEL-8000 at 11/10/14 1:57 PM:
-----------------------------------------------------------------
Reopened. The DefaultCamelContextRegistry contract has been weakened by [this|https://github.com/apache/camel/commit/cdee7809bf801faf504d06047d5763d57bc4067f] commit.
The DefaultCamelContextRegistry implementation gives package protected access to add/remove camel contexts to the camel runtime. Clients are not expected to manage the set of registered contexts.
Registered listeners are owned by the client which registered the listener.
Neither the camel runtime nor non-owning clients can control the set of registered the listeners.
was (Author: tdiesler):
Reopened. The DefaultCamelContextRegistry contract has been weakened by [this](https://github.com/apache/camel/commit/cdee7809bf801faf504d06047d5763d57bc4067f) commit.
The DefaultCamelContextRegistry implementation gives package protected access to add/remove camel contexts to the camel runtime. Clients are not expected to manage the set of registered contexts.
Registered listeners are owned by the client which registered the listener.
Neither the camel runtime nor non-owning clients can control the set of registered the listeners.
> 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)