Hi,
Ok, it works with direct: component. Does it mean the seda: component is
InOnly in Camel 1.x ?
For my information, does Camel 2.x wait for the reply with seda: components
?
How can I set an InOnly MEP on one of the route called by the pipeline,
direct:rs1 for example ?
from("direct:rs1").setExchangePattern(ExchangePattern.InOnly).bean(cb).to(LOG);
?
Thank you very much for your help !
Raphaël
2010/1/12 Claus Ibsen <[email protected]>
> Hi
>
> Use direct:rs1 ... rs3 instead of seda as Camel 1.x does not wait for
> the "reply" so to speak.
>
> And it does depend which MEP you use. InOnly or InOut etc.
>
>
> 2010/1/12 Raphaël Delaporte <[email protected]>:
> > Hi,
> >
> > There is something I do not understand in the Pipeline processor.
> > Let's consider the following route declaration :
> >
> > from("seda:pipeline").pipeline("seda:rs1","seda:rs2","seda:rs3");
> >
> > ChangeBody cb = new ChangeBody();
> > from("seda:rs1").bean(cb);
> > from("seda:rs2").bean(cb);
> > from("seda:rs3").bean(cb).to("log:pipeline?showAll=true");
> >
> >
> > With ChangeBody, a simple bean to concat twice body.
> > static public class ChangeBody{
> > public String change(@Body String body) throws Exception {
> > return body + body;
> > }
> > }
> >
> >
> > For example, if I inject the "a" body message, I would expect to have
> > "aaaaaaaa"(2*2*2) in the log message, but I've just got "aa".
> > What have I miss ? (I'm using 1.6.0 version since I use Camel in SMX
> 3.3).
> >
> > Thanks all.
> > Raphaël
> >
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
