camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Diesler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-8000) Container API not usable in WildFly
Date Thu, 06 Nov 2014 14:13:34 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Diesler updated CAMEL-8000:
----------------------------------
    Description: 
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.

  was:
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, 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.


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

Mime
View raw message