You'll want to use the bundle plugin and create a blueprint.xml to bootstrap your Camel Java DSL. I use the Camel Java DSL all the time in Blueprint for a variety of reasons (testing is easier as the RouteBuilders exist without the camel context). I’m not sure why your Camel blueprint archetype is blowing up but I’d start with that first but then you’ll have to modify the blueprint file to add your
Here's a snippet: <bean class="foo.bar.MyFirstRouteBuilder" id="firstRouteBuilder"/> <bean class="foo.bar.MySecondRouteBuilder" id="secondRouteBuilder"/> <camelContext id="document-logic-service"xmlns="http://camel.apache.org/schema/blueprint"> <routeBuilder ref="firstRouteBuilder"/> <routeBuilder ref="secondRouteBuilder"/> </camelContext> The RouteBuilders can be independently unit tested then with CamelTestSupport outside the Blueprint container. This also allows an injection and setup to take place for your route builders when they are instantiated and then when the Camel context is given their reference. Without that step Camel and Felix/Karaf are unaware of their existence. If you can’t get the archetype to run and create a Camel Blueprint project for you, I’d Google around for a sample project that has the POM correct. Generally I'll have a features file and configuration file associated with the project as well so that the features repository can be added and installed. There may be a better way to do this with profiles in Karaf 4 but I'm a bit behind the times in that regard. Ranx -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html