camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6338) camel-cdi shouldn't use deltapsike bean manager provider in the CamelExtension
Date Sun, 02 Mar 2014 11:29:19 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917368#comment-13917368
] 

Claus Ibsen commented on CAMEL-6338:
------------------------------------

Patches is welcome.

> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message