svn commit: r899772 - in /websites/staging/deltaspike/trunk/content: ./ jsf.html

[bu...@apache.org]

Author: buildbot
Date: Sun Mar  2 21:45:04 2014
New Revision: 899772

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/jsf.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Mar  2 21:45:04 2014
@@ -1 +1 @@
-1573373
+1573374

Modified: websites/staging/deltaspike/trunk/content/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/jsf.html Sun Mar  2 21:45:04 2014
@@ -363,7 +363,7 @@ The best way, to apply it for all views,
 
 
 <h2 id="viewaccessscoped-since-06">@ViewAccessScoped (since 0.6)</h2>
-<p>In case of conversations you have to un-scope beans manually (or they we be terminated automatically after a timeout). However, sometimes you need beans with a lifetime which is as long as needed and as short as possible - which are terminated automatically (as soon as possible). In such an use-case you can use this scope. The simple rule is, as long as the bean is referenced by a page - the bean will be available for the next page (if it's used again the bean will be forwarded again). It is important that it's based on the view-id of a page (it isn't based on the request) so e.g. Ajax requests <b>don't</b> trigger a cleanup if the request doesn't access all view-access scoped beans of the page. That's also the reason for the name @<em>View</em>AccessScoped.</p>
+<p>In case of conversations you have to un-scope beans manually (or they will be terminated automatically after a timeout). However, sometimes you need beans with a lifetime which is as long as needed and as short as possible - which are terminated automatically (as soon as possible). In such an use-case you can use this scope. The simple rule is, as long as the bean is referenced by a page - the bean will be available for the next page (if it's used again the bean will be forwarded again). It is important that it's based on the view-id of a page (it isn't based on the request) so e.g. Ajax requests <b>don't</b> trigger a cleanup if the request doesn't access all view-access scoped beans of the page. That's also the reason for the name @<em>View</em>AccessScoped.</p>
 <div class="codehilite"><pre><span class="nd">@ViewAccessScoped</span>
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">WizardBean</span> <span class="kd">implements</span> <span class="n">Serializable</span>
 <span class="o">{</span>