camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Matèrne (jhm) <>
Subject AW: Any issues having Camel Processor doing all the Works
Date Fri, 12 Aug 2016 12:59:46 GMT
Of course you could do all in plain Java.
Using Camel introduces a lot of dependencies and you have to think about its
benefits and drawbacks (as by each architectural decision).

What you earn (IMO):
- code is easier to read
- easier asynchronous behaviour
- easier integration with other technologies

And of course, learning new things requires time.
You have to decide if it's worth (for you/your project).


> -----Urspr√ľngliche Nachricht-----
> Von: JamesG []
> Gesendet: Donnerstag, 11. August 2016 18:52
> An:
> Betreff: Any issues having Camel Processor doing all the Works
> Hi,
> Instead of doing the routing using DSL, web service calling with CXF
> component, enriching, intercepting, etc , why not just have a Processor
> and put all the java codes there? For a Camel beginner, this seems
> pretty much easier to get the things done (definitely for those with
> java background), but I am not sure how effective or correct this
> approach is.
> Below is a sample scenario:
> 1)  Call a web service to retrieve some result.
> 2)  Based on the result, decide whether to proceed calling another
> service.
> If I would to achieve the above through Processor, it's merely few
> lines of codes.
> But if I'm using DSL to do it, the work is going to be more (cxf
> endpoint, enrich, when, simple).
> Appreciate any advises and comments.
> Thanks in advance.
> --
> View this message in context:
> issues-having-Camel-Processor-doing-all-the-Works-tp5786330.html
> Sent from the Camel - Users mailing list archive at

View raw message