Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of dwhytock@gmail.com designates
 74.125.83.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=FEisP3PmcunRCyJ6gOLjcPDTUSRfLZJtwy0BychU3cM2A/nU2LY/DRglrLeUkuC1iK
         3C51uh+me891poKP+iUQfzCMpCaxxArs1Tga5XDoKcfeGStuQRl0lmiZSH6Z/4/MGG1x
         fkHj3hD48Y//iz1eyV3A6pQig3Ci0O1bgBD28=
MIME-Version: 1.0
In-Reply-To: <BANLkTi=1OUL_SUPHnYX__21SZ+gcqyPfxA@mail.gmail.com>
References: <BANLkTi=1OUL_SUPHnYX__21SZ+gcqyPfxA@mail.gmail.com>
Date: Fri, 27 May 2011 12:54:15 -0400
Message-ID: <BANLkTinBR2Tc6viPA3Ku5SMDQGGqSf2Zog@mail.gmail.com>
Subject: Re: Loop usage
From: Donald Whytock <dwhytock@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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 <gregory.mcfall@gmail.com> 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
>