Yeah When you use OSGi its recommended to use the blueprint archetype that creates a blueprint xml file. This is needed as then you let blueprint bootstrap the application.
If you dont have that, its much more manual work to do that in OSGi where you need to use an OSGi Service Activator and 10 other things to setup Camel et all for OSGi. So having the blueprint xml file, you just define a <camelContext> and then you can configure it to use Java DSL route builders for the routes. That is the same if you use a spring xml file as well. You can use Java DSL routes and also the XML together. See details in the CiA book chapter 2, section 2.4.3, and on the website you can find some details at http://camel.apache.org/spring.html And for blueprint http://camel.apache.org/using-osgi-blueprint-with-camel.html Notice the <camelContext> in Spring and Blueprint is 99,9% identical (there is some TX stuff pending for blueprint, but otherwise they are the same). So when you see some spring examples they are easily transfferable to blueprint. On Fri, Nov 1, 2013 at 3:08 PM, John Dubchak <[email protected]> wrote: > Hi, > > I am in the process of building routes, starting with the interactive > archetypes, and was wondering why there are archetype projects for > camel-blueprint, spring-dm, and cxf-contract-first-blueprint that are all > OSGi "ready", but nothing for a Java DSL project. Is it possible to create > an OSGi "ready" Java DSL-based project to drop into ServiceMix? > > Thanks, > John -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
