camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "raffi.onjava" <>
Subject RE: java dsl vs blueprint xml
Date Wed, 16 Dec 2015 05:21:47 GMT
Strange why the groovy DSL isn't more common; to me it looks much cleaner
and elegant compared to Java and XML.


-----Original Message-----
From: souciance [] 
Sent: Tuesday, December 15, 2015 9:01 AM
Subject: java dsl vs blueprint xml


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
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?


View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message