On Tue, 12 Apr 2011 13:52:10 -0300, Christophe Cordenier
<christophe.corden...@gmail.com> wrote:
My response is not directly related to your question, by the way... in
previous version of T5 it was possible to initiliaze the value of
persistent variables at declaration time. And this value was considered
as the default value. This feature was the cause of session conflicts,
more precisely, i
think it was javassist that was the root cause,
Javassist wasn't the root cause. It was a problem with the page pool, more
specifically, the field having its value reset to the initial value. When
it wasn't an atomic value, one user could see data from other user.
--
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
