camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: seda & concurrent consumers
Date Thu, 24 May 2012 08:46:37 GMT
On Thu, May 24, 2012 at 9:42 AM, ppou <panadp@gmail.com> wrote:
> I have a requirement to route exchanges sequentially to a POJO processors.
>
> I am trying something like the following:
>
> .from("direct:start")
> .to("xslt:xslt/transform.xsl")
> .to("seda:In");
>
> from("seda:In?concurrentConsumers=1").to("bean:rsProcessor");
>
>
> The bean processor is sending the body payload to an external service using
> a socket, and it should wait to read a response before sending the new
> request.
>
> I thought I could ensure this operation with concurrentConsumers=1 in the
> seda component. Is this not the case?
>
> How can I achieve such an operation?
>

Then let the bean wait for the reply.
What do you do in the bean code?
You would need to have the bean block/wait for the reply.

> Regards,
>
> Panos
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/seda-concurrent-consumers-tp5713463.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message