Em Tue, 03 Mar 2009 23:28:50 -0300, Luther Baker <lutherba...@gmail.com>
escreveu:
Clarification for me - I know that Tapestry creates "pools" of my pages.
Conceptually, I've often wondered how it does that - ie: does it nullify
all the fields between requests?
It depends on the field. I don't know what happens when the field is
controlled by Tapestry (@Inject, @InjectComponent, @Component, etc).
AFAIK, for ordinary fields, Tapestry sets each field with its initial
value when a page is returned to the pool, unless it is annotated with
@Retain. In this case, the fields is left as is.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
