camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vitalii Tymchyshyn <>
Subject Re: Any issues having Camel Processor doing all the Works
Date Fri, 12 Aug 2016 13:03:11 GMT
Look at it as data flow vs IoC. It's much easier to split data flow to
parallelize of externalize some part. Especially since Camel is able to do
this in non-blocking way. I am able to process few hundred simultanious
requests in few threads without adaptation of the beans to non-blocking or
concurrent calls, just by using camel.

Best regards, Vitalii Tymchyshyn

Пт, 12 серп. 2016 05:13 користувач JamesG <> пише:

> 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:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message