You could have a bean or processor check the data and set the next route in a header. Then use .toD after the bean/processor to send to the proper next step.
Steve Huston (sent from my iPhone - please excuse brevity and typos) > On Nov 30, 2016, at 9:27 AM, spurcell <scott_purc...@mastercard.com> wrote: > > In a project I am working on, I am parsing a large excel file, and during the > routing, I am performing some validation on the data. I have a route that > performs the validation, and if validation is good, I want to continue down > the same routes that exist. But if the data is invalid, I want to pass it to > a different route to process and handle database writes there. > > I have went through all the EIP patterns, but do not see one that performs > what I call a sift, where the good ones go down one path and the bad ones go > down a different path. > > Can someone assist with possible work arounds for this? > > Thanks > Scott > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Route-to-two-paths-tp5790803.html > Sent from the Camel - Users mailing list archive at Nabble.com.
