Thanks alot Claus. It was a silly mistake. I realized that I was referencing the bean with its class name and not its id. Its now working fine.
Claus Ibsen-2 wrote: > > On Tue, Jun 15, 2010 at 10:08 AM, Claus Ibsen <[email protected]> > wrote: >> On Mon, Jun 14, 2010 at 12:26 PM, M.Ismail <[email protected]> >> wrote: >>> >>> Although I changed the boolean variable to volatile it only stored its >>> value >>> through the flow of a single message (i.e. in the next processor the new >>> value is available).However, after I received another request message it >>> lost its new value. am I missing something here? >>> >> >> I created an unit test which uses a stateful bean in a Camel route >> http://svn.apache.org/viewvc?rev=954742&view=rev >> > > Ups it was this commit > http://svn.apache.org/viewvc?rev=954743&view=rev > > > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > > -- View this message in context: http://old.nabble.com/Saving-Login-state-in-the-route-tp28865247p28889974.html Sent from the Camel - Users mailing list archive at Nabble.com.
