Hi
I think you can just define the route like this.
from("xxx")
.to(ENDPOINT1)
.process("prepare request")
.to(ENDPOINT2)
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, August 7, 2013 at 3:56 AM, mateo wrote:
> But to create request for ENDPOINT2 I need two things: original request (the
> one which was on Exchange while entering multicast) and response from
> ENDPOINT1. And doing this in proposed way I will lost request information
> (in Exchange in out there will be only response from ENDPOINT1).
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Multicast-with-two-endpoints-when-request-to-the-second-depends-on-the-response-from-the-first-one-tp5736859p5736868.html
> Sent from the Camel - Users mailing list archive at Nabble.com
> (http://Nabble.com).
