Author: hlship
Date: Thu Nov 6 15:05:10 2008
New Revision: 712003
URL: http://svn.apache.org/viewvc?rev=712003&view=rev
Log:
TAP5-206: Document that you should not instantiate an @Persist field in its
declaration
Modified:
tapestry/tapestry5/trunk/src/site/apt/guide/persist.apt
Modified: tapestry/tapestry5/trunk/src/site/apt/guide/persist.apt
URL:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/src/site/apt/guide/persist.apt?rev=712003&r1=712002&r2=712003&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/src/site/apt/guide/persist.apt (original)
+++ tapestry/tapestry5/trunk/src/site/apt/guide/persist.apt Thu Nov 6 15:05:10
2008
@@ -86,16 +86,7 @@
Default Values
- As with other fields, a default value may be specified inline, or inside a
constructor.
-
- This value is retained and used to reset the value of the field at the end
of each request,
- before the page is returned to the page pool.
-
- Handling of the null value can be a tricky case, due to the limitations of
the underlying
- Servlet API. Changing a persistent field's value to null <removes> the
- field's attribute from the session. On later requests, the field will reset
to its
- default value. Since that is usually null, this is not a problem ... it is
only a problem
- if a field has a non-null default value and may be changed to null.
+ Fields marked with @Persist may not have default values (whether set inline,
or inside a constructor).
Clearing Persistent Fields
