[
https://issues.apache.org/jira/browse/CAMEL-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216115#comment-14216115
]
ASF GitHub Bot commented on CAMEL-8059:
---------------------------------------
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/334
[CAMEL-8059] Add CamelContext creation hook
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-8059
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/334.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 #334
----
commit 69a9f60b77418499007bed2c34190dd012300672
Author: Thomas Diesler <[email protected]>
Date: 2014-11-18T11:57:09Z
[CAMEL-8059] Add CamelContext creation hook
----
> Add CamelContext creation hook
> ------------------------------
>
> Key: CAMEL-8059
> URL: https://issues.apache.org/jira/browse/CAMEL-8059
> Project: Camel
> Issue Type: Task
> Reporter: Thomas Diesler
> Fix For: 2.14.1, 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
