[CAMEL-4685] Camel blueprint does not work with Aries blueprint 0.4

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.8.2, 2.9.0
• Component/s: camel-blueprint
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Stephan Siano
• Created: 16/Nov/11 09:01
• Updated: 07/May/13 10:57
• Resolved: 07/May/13 10:57

Description

Camel blueprint does only work in conjunction with Aries blueprint 0.3, it fails with the current release 0.4.

The issue is somewhat related to CAMEL-4543 (completely removing the hard dependency to aries blueprint would of course also fix the dependency to a specific aries blueprint version).

The reason behind that version dependency is that the ExtendedBlueprintContainer inteface was moved from org.apache.aries.blueprint to org.apache.aries.blueprint.services between versions 0.3 and 0.4. The interface is referenced from the CamelContextFactoryBean and CamelProxyFactoryBean. I am not completely sure, but I guess that the lookup of the blueprint bundle context could also be performed in some other way.