Thank you Henryk,
Your solution has worked for me.
Note: I had to get the original exchange from inside one of the returned
(multicast) exchanges to get the original headers and make sure they were
preserved.
This was done inside a Processor implementation.
Once again, thank you
Regards,
Emeka
> I'm having an issue as well, for which I have implemented the
> AggregationStrategy but am still facing issues.
This is how you can collect exchanges multicasted to the several endpoints.
from("direct:multicastMe")
.multicast(new GroupedExchangeAggregationStrategy()).parallelProcessing()
Hello Tyler,
Did you ever fix this problem?
I'm having an issue as well, for which I have implemented the
AggregationStrategy but am still facing issues.
Please see the URL below for more details.
http://fusesource.com/forums/thread.jspa?threadID=3942&tstart=0
Thank you for any help you can pr
Hi
Yogesh is right when he suggest to use the aggregation strategy of the
multicast. This allows you full control of the assembly of the
outgoing message when all the parallel multicasted messages is
complete.
By default the multicast will just keep the last message as the
outgoing message. (eg
Hi Tyler,
Are some of the headers in there but not all of them? If you want, you can
use an aggregator with the multicast and set a custom aggregation strategy:
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html
This way you can
