released any 1.5.2 release. In fact neither a 1.5.1 release.
>> The latest is 1.6.1. Is it that release you are using?
>>
>> Anyway it should work on 1.6.1.
>>
>> Mind that you have to take care in your custom aggregator whether you
>> store the aggregated res
>>
>> Mind that you have to take care in your custom aggregator whether you
>> store the aggregated response
>> in either IN or OUT. It is in fact safest to store it in OUT.
>>
>>
>>
>>> Thanks,
>>> Chris
>>> --
>>> View
.6.1.
>
> Mind that you have to take care in your custom aggregator whether you
> store the aggregated response
> in either IN or OUT. It is in fact safest to store it in OUT.
>
>
>
>> Thanks,
>> Chris
>> --
>> View this message in context:
>
ther IN or OUT. It is in fact safest to store it in OUT.
> Thanks,
> Chris
> --
> View this message in context:
> http://www.nabble.com/Custome-aggregator-for-splitter-in-camel-1.5.2-tp23970911p23970911.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
&
ct in 1.5.0: https://issues.apache.org/activemq/browse/CAMEL-1041.
Should it be fixed in 1.5.2?
Thanks,
Chris
--
View this message in context:
http://www.nabble.com/Custome-aggregator-for-splitter-in-camel-1.5.2-tp23970911p23970911.html
Sent from the Camel - Users mailing list archive at Nabble.com.
