[
https://issues.apache.org/jira/browse/CAMEL-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-7760:
-------------------------------
Fix Version/s: (was: 2.14.2)
(was: 2.15.0)
2.16.0
> WELD-001409: Ambiguous dependencies for type CdiCamelContext
> ------------------------------------------------------------
>
> Key: CAMEL-7760
> URL: https://issues.apache.org/jira/browse/CAMEL-7760
> Project: Camel
> Issue Type: Bug
> Components: camel-cdi
> Affects Versions: 2.13.2
> Environment: JBOSS_HOME: "D:\wildfly-8.1.0.Final"
> JAVA: "D:\jdk1.8.0_11\bin\java"
> Reporter: Markus Eisele
> Priority: Minor
> Fix For: 2.16.0
>
>
> Trying to bootstrap camel in a @singleton @startup bean with enabled CDI
> leads to a deployment exception.
> Ambiguous dependencies for type CdiCamelContext with qualifiers @Default
> - org.apache.camel.cdi.internal.CamelContextBean@35921a07,
> - Managed Bean [class org.apache.camel.cdi.CdiCamelContext] with qualifiers
> [@Any @Default]
> The only way to workaround this, is to implement a custom Cdi-Extension to
> veto the bean in question.
> Here is a demo-app: https://github.com/myfear/CamelEE7/
> (including workaround)
> The deployment exception:
> https://gist.github.com/myfear/40bfc75c292dafa7ba64
> This should be solved in order to make it easier to use Camel on EE servers
> with CDI integration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
