it
> easier.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775124.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Matt Sicker
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 -
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.
-vs-blueprint-xml-tp5775085p5775097.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
context:
http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775095.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Great example, thanks, I think that seems to be the best approach going
forward. You basically get the best from both worlds.
--
View this message in context:
http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775097.html
Sent from the Camel - Users mailing list archive at
camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775091.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
the
second step deploy to a docker container.
Ok so it seems the best approach seems to be a mix of both where blueprint
can be used to register services.
--
View this message in context:
http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775094.html
Sent from the Camel - Use
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:
http://camel.465427.n5.nabble.com/java-dsl-vs-blueprin
Thanks for the tip Christian. I haven't tried that before.
So basically, just like any other bean you just "ref-it" and inside is a
standard routebuilder.
I will give it a go and try that.
--
View this message in context:
http://camel.465427.n5.nabble.com/java-dsl-v
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
>
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):
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
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.
14 matches
Mail list logo
