Author: hlship
Date: Sun Aug 17 07:05:06 2008
New Revision: 686613
URL: http://svn.apache.org/viewvc?rev=686613&view=rev
Log:
TAPESTRY-2595: Application State Objects are not persisted back to the session
at the end of the request
Modified:
tapestry/tapestry5/trunk/src/site/apt/guide/appstate.apt
Modified: tapestry/tapestry5/trunk/src/site/apt/guide/appstate.apt
URL:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/src/site/apt/guide/appstate.apt?rev=686613&r1=686612&r2=686613&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/src/site/apt/guide/appstate.apt (original)
+++ tapestry/tapestry5/trunk/src/site/apt/guide/appstate.apt Sun Aug 17
07:05:06 2008
@@ -12,7 +12,11 @@
Instead, you want to use an <Application State Object> (an ASO).
With an ASO, the value is automatically stored outside the page; with the
default storage strategy, it is stored in the session.
-
+
+ <Note: Tapestry's naming convention here is in conflict with naming
conventions of the Servlet API. Do not be confused: ASOs are
+ stored (by default) in the session, not the servlet context. They are
unique to an individual user, not shared between users. >
+
+
A field holding an ASO is marked with the
{{{../apidocs/org/apache/tapestry5/annotations/ApplicationState.html}ApplicationState}}
annotation.