Why do you need to intercept those endpoints? Do you plan to use it in your unit test?
-- 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, April 17, 2013 at 5:03 AM, RTernier wrote: > I don't think the splitter can do what I want. > > I want to take a single message, transform that message into X messages > (sometimes it might split, other times I'll have to take the original > incoming message, transform it based on an element based inside the > message). > > Looking at other forums, someone mentioned the Load Broker Example > <https://cwiki.apache.org/CAMEL/loan-broker-example.html#LoanBrokerExample-Implementationwithwebservice> > > > > I thought about running multicast/parallelProcessing/to(1, 2, 3, 4 etc.) > which would send the same message, and I could intercept those... > (interceptSendToEndpoint) > > would that be a better way of doing this? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Splitting-XML-into-multiple-separate-bits-and-send-out-to-webservices-tp5730936p5730985.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
