A custom AggregationStrategy in the multicast will not work?
Otherwise you could use the enrich() DSL...

Best,
Christian
Am 23.08.2013 23:59 schrieb "abdiels" <[email protected]>:

> Christian,
>
>      Thank you for your reply; however, it is not that simple.  The message
> that will continue is dependent on the answer from the component.  So think
> about it this way, we send to some validation out of that we get a report
> with the results which needs to go to the client; however, some clients
> don't want to stop even if validation fails so the main message has to
> continue.  I hope you see that multicast will not work since the multicast
> will only get the "out" message from the previous component and not the
> original "in".  In my case I want to go to a component and after that
> component executes, I want to do something else with the message that went
> into that component and the message that resulted from that component.
>
> Thank you,
>
> Abdiel
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/How-to-process-a-response-and-the-original-message-after-submitting-to-a-component-tp5737841p5737845.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Reply via email to