You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2014/11/06 16:26:33 UTC
[jira] [Issue Comment Deleted] (CAMEL-8000) Container API not
usable in WildFly
[ https://issues.apache.org/jira/browse/CAMEL-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-8000:
-------------------------------
Comment: was deleted
(was: This blocks the insight-camel integration for Fuse-6.2 on EAP-6.4
https://issues.jboss.org/browse/ENTESB-2173)
> Container API not usable in WildFly
> -----------------------------------
>
> 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
>
> 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)