As Christian suggested, blending the two is a good approach. I’ve done that where I’ve used blueprint to register services, but still use the java dsl for everything else.
I wouldn’t worry about deployment as a factor for choosing between the two if you’re using karaf. Sure, dropping an xml file into the deploy directory is nice and easy, and working on it live in that directory is even better. But you can use the bundle:watch command in karaf to monitor maven repos and have it auto-redeploy every time you build. It’s an awesome workflow for your developers. And while you can compile together all your blueprint xmls and deploy if you want to break things down to smaller files (everything in src/main/resources/OSGI-INF will get included automatically), if you want to share code between projects/services, then you’re going to be writing Java code and sharing that anyway using good DI practices. Personally, I use the Java DSL as much as I can, but sometimes need to dip into blueprint. ~Danny On Dec 15, 2015, at 10:05 AM, Christian Schneider <ch...@die-schneider.net> wrote: > How about using blueprint to boot up camel context and still do the dsl in > Java? > You can refer to a bean that represents a RouteBuilder. > > Christian > > On 15.12.2015 15:01, souciance wrote: >> Hello, >> >> We are in a project and have evaluated both the java dsl and blueprint and >> we plan to deploy our routes to Karaf. >> >> I understand that developing using blueprint will make the deployment >> easier. However I have some reservations about blueprint. >> 1) It is in xml and not java so thats additional layer to work with. >> 2) Unlike in the java dsl, you cannot split the routes into several files >> and import them. >> 3) A lot of the documentation provides most of the examples for the java >> dsl. >> 4) The java dsl is easier to read for existing java developers. >> 5) Will blueprint exist in 5 years? >> >> Do you as Camel users/developers have any specific thoughts on this? >> >> Best >> Souciance >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085.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 >
