My mistake; transient page properties do work this way.
At the core of it is a pair of fields. During containingPageDidLoad(), the value of the original field is copied to the default field. On containingPageDidDetach(), the default field is copied over the original field. On 9/13/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Sounds cool :) Do properties work in a similar fashion now as well? On 9/13/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > Just made component parameters smarter. > > First, you can set default values for components, just by updating the > fields. I.e. > > @Parameter > private int count = 5; > > That value, 5, becomes the default value if the parameter is not bound. It > also is the value the field is reset to after the component renders. > > And parameters that are not bound can be read and updated with no side > effects. This removes the need for isBound() checks before reading or > updating a parameter. > > I'm going to document this, this afternoon. > > -- > Howard M. Lewis Ship > TWD Consulting, Inc. > Independent J2EE / Open-Source Java Consultant > Creator and PMC Chair, Apache Tapestry > Creator, Apache HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > -- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
