On Mon, 22 Feb 2010 21:57:22 -0300, Hilco Wijbenga
<hilco.wijbe...@gmail.com> wrote:
On 22 February 2010 12:48, Howard Lewis Ship <hls...@gmail.com> wrote:
In all cases where Tapestry needs to access the field, such as to
synchronize its value with the session, it bypasses getters and
setters (either yours, or those generated by @Property) and updates
the field directly.
So what happens if I have something like
Thing getThing() { return model.getThing(); }
void setThing(Thing thing) { model.setThing(thing); }
? Or any other scenario where there is no easily identifiable field?
It works normally. Howard was talking specifically about *fields* with the
@Persist annotation (@SessionState too).
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, 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
