Could be a bug there; I'll have to figure out how to handle it
properly; likely, it will involve pre-emptively loading values from
the session when the page is "attached" to the request, rather than
waiting until the field value is actually accessed.
On Mon, Apr 23, 2012 at 9:14 AM, Luke Wilson w
Hi,
The following documentation in ComponentResources is misleading in Tapestry
5.3.2.
/**
* Discards all persistent field changes for the page containing the
component. Changes are eliminated from
* persistent storage (such as the {@link
org.apache.tapestry5.services.Session}) w
