Re: java dsl vs blueprint xml

How much cleaner is the Groovy DSL compared to using Java 8 with the Java DSL? On 16 December 2015 at 02:10, souciance wrote: > I wouldn't mind using it but considering that most of the books and > documentation is using the java or blueprint dsl so that makes

RE: java dsl vs blueprint xml

I wouldn't mind using it but considering that most of the books and documentation is using the java or blueprint dsl so that makes it a bit easier. -- View this message in context: http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775124.html Sent from the Camel - Users

RE: java dsl vs blueprint xml

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

Re: java dsl vs blueprint xml

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

Re: java dsl vs blueprint xml

I have used direct-vm for that for some integrations, only difference is that with direct-vm you get multiple camel-context. I haven't tried your spring example in blueprint to see if it works though. -- View this message in context:

Re: java dsl vs blueprint xml

Btw. You can also combine this with the blueprint-maven-plugin from Aries. http://aries.apache.org/modules/blueprint-maven-plugin.html You still have to define the camel-context in a blueprint file but you can define all other beans using annotations. See:

Re: java dsl vs blueprint xml

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

Re: java dsl vs blueprint xml

2) Unlike in the java dsl, you cannot split the routes into several files and import them. you can use http://camel.apache.org/direct-vm.html or http://camel.apache.org/vm.html to communicate beetwen different routes; you can share single Camel context between route builders (Spring example):

Re: java dsl vs blueprint xml

Yeah, I will probably blend the two approaches and use blueprint to register services and try to use the java dsl as much as possible. I haven't used the auto-deploy feature and that sounds awesome, although in this specific case we'll be using jenkins to build the jar files and in the second

Re: java dsl vs blueprint xml

Yes. here is an example: https://github.com/cschneider/Karaf-Tutorial/blob/master/camel/jms2rest/src/main/java/net/lr/tutorial/karaf/camel/jms2rest/Jms2RestRoute.java https://github.com/cschneider/Karaf-Tutorial/blob/master/camel/jms2rest/src/main/resources/OSGI-INF/blueprint/blueprint.xml

Re: java dsl vs blueprint xml

By the way, if you do blend the two, how do you handle code for error handling, logging and similar parts? Do you put that in the routebuilder as well or in the blueprint? In essence, the blueprint just loads the bean and that is it, it just acts as a startup mechanism. -- View this message in