Author: buildbot Date: Sat Feb 15 11:58:35 2014 New Revision: 898014 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 Sat Feb 15 11:58:35 2014 @@ -1 +1 @@ -1568619 +1568620 Modified: websites/staging/deltaspike/trunk/content/jsf.html ============================================================================== --- websites/staging/deltaspike/trunk/content/jsf.html (original) +++ websites/staging/deltaspike/trunk/content/jsf.html Sat Feb 15 11:58:35 2014 @@ -120,10 +120,10 @@ <li><a href="#based-scopes">Based Scopes</a></li> </ul> </li> -<li><a href="#scopes-todo">Scopes (TODO)</a><ul> +<li><a href="#scopes">Scopes</a><ul> <li><a href="#windowscoped">@WindowScoped</a></li> -<li><a href="#viewaccessscoped">@ViewAccessScoped</a></li> -<li><a href="#groupedconversationscoped">@GroupedConversationScoped</a></li> +<li><a href="#viewaccessscoped-since-06">@ViewAccessScoped (since 0.6)</a></li> +<li><a href="#groupedconversationscoped-since-06">@GroupedConversationScoped (since 0.6)</a></li> <li><a href="#viewscoped">@ViewScoped</a></li> <li><a href="#jsf-20-scopes">JSF 2.0 Scopes</a></li> </ul> @@ -332,7 +332,7 @@ The best way, to apply it for all views, <li>@ViewAccessScoped</li> <li>@GroupedConversationScoped</li> </ul> -<h1 id="scopes-todo">Scopes (TODO)</h1> +<h1 id="scopes">Scopes</h1> <h2 id="windowscoped">@WindowScoped</h2> <p>The window-scope is like a session per window. That means that the data is bound to a window/tab and it not shared between windows (like the session scope does). Usually you need the window-scope instead of the session-scope. There aren't a lot of use-cases which need shared data between windows.</p> <div class="codehilite"><pre><span class="nd">@WindowScoped</span> @@ -343,7 +343,7 @@ The best way, to apply it for all views, </pre></div> -<h2 id="viewaccessscoped">@ViewAccessScoped</h2> +<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> <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> @@ -355,7 +355,7 @@ The best way, to apply it for all views, <p>Hint: <br/> @ViewAccessScoped beans are best used in conjunction with the <code>CLIENTWINDOW</code> window handling, which ensures a clean browser-tab separation without touching the old windowId. Otherwise a 'open in new tab' on a page with a @ViewAccessScoped bean might cause the termination (and re-initialization) of that bean.</p> -<h2 id="groupedconversationscoped">@GroupedConversationScoped</h2> +<h2 id="groupedconversationscoped-since-06">@GroupedConversationScoped (since 0.6)</h2> <p>See <a href="#grouped-conversations">(Grouped-)Conversations</a></p> <h2 id="viewscoped">@ViewScoped</h2> <p>DeltaSpike provides an CDI context for the JSF 2.0/2.1 @javax.faces.bean.ViewScoped. You can simply annotate your bean with @javax.faces.bean.ViewScoped and @Named.</p>