Since Camel is using Pipeline to chain to endpoints together, the out
message which comes from first endpoint will be treat as in message for
the second endpoint; if there is on out message that be set to exchange
from first endpoint, second endpoint can still can get the in message
from first
Maybe it will make sense if you consider the aggregation is been done over
incoming messages.
Cheers,
Bruno
On Nov 16, 2009 2:28pm, Wilson wrote:
Hi Claus,
I was out on vacation so my feedback is a bit late.
I figured out why my code is not working.
Your AggregationStrategy
Hi Claus,
I was out on vacation so my feedback is a bit late.
I figured out why my code is not working.
Your AggregationStrategy implementation is setting the message body this
way:
oldExchange.getIn().setBody(oldBody + "," + newBody);
My code is doing this:
oldExchange.getOut().setBody(ol
Hi
See this unit test which I have created that works.
http://svn.apache.org/viewvc?rev=828961&view=rev
On Wed, Oct 21, 2009 at 8:15 PM, Wilson wrote:
>
> Hi Claus,
>
> Thanks for your answer.
>
>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> Do you "loose" message every time you run the unit test?
>>
Hi Claus,
Thanks for your answer.
Claus Ibsen-2 wrote:
>
> Hi
>
> Do you "loose" message every time you run the unit test?
>
> Have you tried with a higher batch timeout?
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://dav
Hi
Do you "loose" message every time you run the unit test?
Have you tried with a higher batch timeout?
On Tue, Oct 20, 2009 at 4:43 PM, Wilson wrote:
>
> Hi,
>
> I am using an aggregator to concatenate the body of a bunch of messages into
> a single message. The following code illustrates the
