camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Pipeline for single processor - any side effect?
Date Tue, 28 Feb 2017 14:58:23 GMT

This is the behavior of 2.x and the EIPs and routing engine is
optimized / doing this.

We have already done too many changes IMHO in 2.19.x and should not do
more changes for the sake of a change.

Camel 3.0 allows to revisit the routing engine and exchange copy stuff
that happens.

You are welcome to log a JIRA for 3.0.

On Tue, Feb 28, 2017 at 3:41 PM, Tomohisa Igarashi
<> wrote:
> Hi,
> I noticed that if eventDrivenProcessors contains only one processor, IN
> message is not copied to OUT even when exchange pattern is InOut while it
> does if it contains multiple processors.
> eventDrivenProcessors are wrapped with Pipeline here when initiating a camel
> route here:
> But if there's only one event driven processor, the processor itself is used
> instead of wrapping with Pipeline:
> Pipeline copies the IN message to OUT if it's InOut and OUT message doesn't
> exist:
> So the IN->OUT copy happens only if multiple processors exist. It means that
> whether the response message is returned as OUT or IN depends on if the
> route results in single processor or not. I think it looks a bit confusing
> and wondering if we can just wrap it with the Pipleline even if there's
> single processor. Is there any undesirable side effect to doing that?
> Thanks,
> Tomo

Claus Ibsen
----------------- @davsclaus
Camel in Action 2:

View raw message