camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Best Practice fro Thread Safe processor
Date Fri, 08 Apr 2011 07:34:21 GMT
On Fri, Apr 8, 2011 at 7:24 AM, Willem.Jiang <willem.jiang@gmail.com> wrote:
> As Camel has a async process module, you can't know if the processors are
> called in a single thread.
> If you are using the thread local to store the states, it may be massed up.
>
> My suggestion is store the states information into the Exchange,  and Camel
> will make sure it is processed rightly.
>

Yeah you can store state for a given Exchange as properties on it.
There is getter/setter for that.


> Willem
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Best-Practice-fro-Thread-Safe-processor-tp4288973p4290075.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message