Btw. You can also combine this with the blueprint-maven-plugin from Aries. http://aries.apache.org/modules/blueprint-maven-plugin.html
You still have to define the camel-context in a blueprint file but you can define all other beans using annotations.
See: https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-blueprint-cdi Christian On 15.12.2015 15:32, souciance wrote:
Great example, thanks, I think that seems to be the best approach going forward. You basically get the best from both worlds. -- View this message in context: http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775097.html Sent from the Camel - Users mailing list archive at Nabble.com.
-- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com
