[CAMEL-7760] WELD-001409: Ambiguous dependencies for type CdiCamelContext

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.13.2
• Fix Version/s: 2.16.0
• Component/s: camel-cdi

Environment

JBOSS_HOME: "D:\wildfly-8.1.0.Final"
JAVA: "D:\jdk1.8.0_11\bin\java"

• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Markus Eisele
• Created: 28/Aug/14 11:06
• Updated: 20/Nov/15 18:10
• Resolved: 09/Jul/15 11:07

Description

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.

Issue Links

• Is contained by: CAMEL-9201 Improved Camel CDI component