On Wed, Oct 12, 2011 at 2:15 PM, David Karlsen wrote:
> Can I control where camel will put the splitted value - or will it
> always be the body?
If you iterator returns an org.apache.camel.Message instance then
Camel will use that as is. Any other value will be regarded as the
body.
>
> 2011/10
Can I control where camel will put the splitted value - or will it
always be the body?
2011/10/11 Claus Ibsen :
> On Mon, Oct 10, 2011 at 10:26 PM, David Karlsen
> wrote:
>> Hi.
>>
>> I'd like to iterate over a header containing a list and doing a "to
>> uri" for each value.
>> Is this possible?
On Mon, Oct 10, 2011 at 10:26 PM, David Karlsen wrote:
> Hi.
>
> I'd like to iterate over a header containing a list and doing a "to
> uri" for each value.
> Is this possible?
>
> The splitter seems to only support body values, and camel:loop seems
> to be count-oriented.
>
The splitter supports
Hi,
Depending on the behaviour that you are pursuing, and assuming that at some
point you will want to send the exchange to the list of endpoints stored in
your header (either sequentially or in a multicast fashion), you could use
different the different enterprise integration patterns offered by
Hi.
I'd like to iterate over a header containing a list and doing a "to
uri" for each value.
Is this possible?
The splitter seems to only support body values, and camel:loop seems
to be count-oriented.
I could of course loop and use an expression for the list length and
access it by index - but
