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?
Cheers,
Hilco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
