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 2013/05/26 15:09:21 UTC
[jira] [Updated] (CAMEL-6338) camel-cdi shouldn't use deltapsike
bean manager provider in the CamelExtension
[ https://issues.apache.org/jira/browse/CAMEL-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-6338:
-------------------------------
Component/s: camel-cdi
Priority: Minor (was: Major)
Fix Version/s: Future
Issue Type: Improvement (was: Bug)
> camel-cdi shouldn't use deltapsike bean manager provider in the CamelExtension
> ------------------------------------------------------------------------------
>
> Key: CAMEL-6338
> URL: https://issues.apache.org/jira/browse/CAMEL-6338
> Project: Camel
> Issue Type: Improvement
> Components: camel-cdi
> Reporter: Romain Manni-Bucau
> Priority: Minor
> Fix For: Future
>
>
> In an cdi extension the bean manager is injected so camel cdi shouldn't use deltaspike for it.
> A nice side effect of it will be it will remove WARNING
> The only trick it will need will be to give org.apache.camel.cdi.CdiBeanRegistry the bean manager to use. A thread local or delegate (registry.getDelegate()) falling back to DS if null should be fine. It just needs to be resetted after extension startup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira