You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2011/06/27 09:20:47 UTC
[jira] [Reopened] (CAMEL-4146) Add a CamelContext Factory that
should be used to create camel contexts
[ https://issues.apache.org/jira/browse/CAMEL-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet reopened CAMEL-4146:
------------------------------------
Assignee: (was: Claus Ibsen)
The main problem is related to OSGi which require additional parameters such as the BundleContext, spring requires the ApplicationContext, etc...
However, there's still a missing thing, which is to have real global interceptors that would also kick in from any DSL, not only spring/blueprint when deploying in OSGi.
What Camel is missing is really some ways to have a "managed" mode, where a container could have more hands on camel internals.
> Add a CamelContext Factory that should be used to create camel contexts
> -----------------------------------------------------------------------
>
> Key: CAMEL-4146
> URL: https://issues.apache.org/jira/browse/CAMEL-4146
> Project: Camel
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> Fix For: 2.8.0
>
> Attachments: CAMEL-4146.patch
>
>
> We need a way to intercept the creation of CamelContext.
> Maybe using a factory with META-INF/services to point to the default implementation to use.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira