Thanks Thiago! The only thing that didn't seem to work was changing @Persist to
@Persist("flash") When I use Flash I start getting Ajax errors again. With my
limited knowledge my best guess is that the flash persistence isn't keeping the
Item around when Ajax calls are made after the page has been rendered. (The
Ajax on the page is updated fields and adding objects to Item.)
Going back to @Persist works fine, but I want to make sure that it isn't
something that is going to come back to bite me later. Is it better to use
@Persist("flash") where possible just because it reduces the amount of memory
used to hold the session or are there other reasons to avoid @Persist in this
situation.
Thanks again.
Jack
-----Original Message-----
From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com>
Sent: Friday, February 4, 2011 4:10pm
To: "Tapestry users" <users@tapestry.apache.org>
Subject: Re: Object is sticking around between sessions.
I'd suggest using @Persist("flash") and invoking
componentResources.discardPersistentFieldChanges() in the afterRender
event:
void afterRender() {
componentResources.discardPersistentFieldChanges();
}
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
