On Thu, Oct 14, 2010 at 4:06 PM, Willem Jiang <[email protected]> wrote:
>> So, Camel will use the same instance across Camel routes? >> >> I failed to replace the message into getIn().setBody() with the >> message clone. It triggers time out exception. May be it's because I'm >> not quite understand about inOut trick. This situation forces me to >> have Camel call clone-service bean before getting into modification >> bean. And it works. >> > > Deep copying will introduce the performance issue to camel, you have to do > it yourself. Basically Camel will copy the message headers and message body > and exchange properties from first exchange to a new next exchange when it > passes the next exchange to another process. So, it's about performance issue. I see that... What a good explanation! Thanks! -- ~The best men are men who benefit to others http://michsan.web.id 一緒に勉強しましょう! Yang berkualitas memang beda rasanya! http://rizqi-cookies.com
