Over and above looping, should there be a more general-purpose copy mechanism, such as CopyProcessor and a copy() route directive?
Don On Tue, May 31, 2011 at 10:16 AM, Claus Ibsen (JIRA) <j...@apache.org> wrote: > Loop EIP - Add copy option to let it start next loop with a copy of the > original exchange > ----------------------------------------------------------------------------------------- > > Key: CAMEL-4033 > URL: https://issues.apache.org/jira/browse/CAMEL-4033 > Project: Camel > Issue Type: Improvement > Components: camel-core > Affects Versions: 2.7.0 > Reporter: Claus Ibsen > Assignee: Claus Ibsen > Priority: Minor > Fix For: 2.8.0 > > > The Loop EIP will use pipes and filters. So if you loop 3 times, then on the > 2nd and 3rd time its the output from the previous processing that is being > used. > > We should add an option so people can use a copy of the original exchange > instead, so its the same copy being looped on each iteration. > > The wiki documentation should be updated to describe the difference in these > two modes. > > See nabble > http://camel.465427.n5.nabble.com/Loop-usage-tp4432628p4432628.html > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira >
