On Thu, 27 May 2010 23:08:37 -0300, Paul Stanton <p...@mapshed.com.au>
wrote:
Hi all,
Hi!
I've noticed that the value for the apparently persistent field is reset
to null when the second type of ajax requests are made ... this may be
because the actions point to different components as listeners.
How you noticed that? If it was through a debugger, you are looking at a
field which access was replaced by method invocations, so its value may
not be what you expect.
I thought that marking @Persist("session") would mean their values were
stored in the HttpSession until session death or I specifically set the
value to null,
That's exactly what happens. I guess you're misunderstanding something in
your application.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org