How about using Exchange.copy() to pass a copy of the exchange to the downstream processor, so that the original exchange doesn't get changed?
Don On Fri, May 27, 2011 at 12:36 PM, Greg McFall <[email protected]> wrote: > Hi, > > The Camel documentation contains the following statement about the Loop > pattern: > > The Loop allows to process a message a number of times and possibly process > them in a different way. > > This seems to imply that the same input message will be processed by the > downstream pipeline with each subsequent iteration. > But my experience shows that the output from one iteration of the loop is > used as input to the next iteration. > > Is this the expected behavior? > That seems like a strange way to define a loop. > Is there any way to coerce the Loop to operate on the same exact input > message for each iteration? > > Cheers, > Greg McFall >
