Strange why the groovy DSL isn't more common; to me it looks much cleaner and elegant compared to Java and XML.
Raffi -----Original Message----- From: souciance [mailto:souciance.eqdam.ras...@gmail.com] Sent: Tuesday, December 15, 2015 9:01 AM To: users@camel.apache.org Subject: java dsl vs blueprint xml 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.
