camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: setHeaders & processors
Date Wed, 25 May 2011 22:20:31 GMT
my mistake,

i needed a thread local to store the exchange before using it in my
singleton.

sorry for the spam.

- Romain

2011/5/25 Romain Manni-Bucau <rmannibucau@gmail.com>

> oops, i posted too fast,
>
> i missed the splitter int he route:
>
>
> from("file:...).split(...)..streaming().parallelProcessing().inOut("bean:myProcessor").to("bean:checkHeaders").end().to("log:done");
>
> - Romain
>
>
> 2011/5/25 Romain Manni-Bucau <rmannibucau@gmail.com>
>
>> Hi,
>>
>> i have a route with a splitter with parallel processing + streaming.
>>
>> just after the split i run a processor in in-out mode setting some
>> headers.
>>
>> Sometimes (i don't really know when) at the next step the headers i set in
>> the processor are not in current exchange headers.
>>
>> If i replace my processor by setHeader() API (from the fluent API) +
>> simple it works.
>>
>> What could it be?
>>
>> Here is the processor process method:  exchange.getIn().setHeader("FOO",
>> generator.next());
>> Here is the route (in pseudo code):
>> from("file:...).inOut("bean:myProcessor").to("bean:checkHeaders");
>>
>> - Romain
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message