You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@myfaces.apache.org by ma...@apache.org on 2005/08/23 12:05:33 UTC
svn commit: r239388 -
/myfaces/forrest/trunk/content/xdocs/tomahawk/uiSaveState.xml
Author: manolito
Date: Tue Aug 23 03:05:29 2005
New Revision: 239388
URL: http://svn.apache.org/viewcvs?rev=239388&view=rev
Log:
New t:saveState description from Mike Kienenberger
Modified:
myfaces/forrest/trunk/content/xdocs/tomahawk/uiSaveState.xml
Modified: myfaces/forrest/trunk/content/xdocs/tomahawk/uiSaveState.xml
URL: http://svn.apache.org/viewcvs/myfaces/forrest/trunk/content/xdocs/tomahawk/uiSaveState.xml?rev=239388&r1=239387&r2=239388&view=diff
==============================================================================
--- myfaces/forrest/trunk/content/xdocs/tomahawk/uiSaveState.xml (original)
+++ myfaces/forrest/trunk/content/xdocs/tomahawk/uiSaveState.xml Tue Aug 23 03:05:29 2005
@@ -12,6 +12,13 @@
<section>
<title>Description</title>
<p>
+ t:saveState enables you to persist beans and values longer than
+ request scope, but shorter than session scope. It is ideal for
+ persisting backing beans and values with the same scope as your view
+ components. It does this by saving the target state with the
+ component tree.
+ </p>
+ <p>
Traditional JSP Applications save their state information within
HttpSession objects. This is an easy to use but not always satisfying approach:
</p>