deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gpetra...@apache.org
Subject svn commit: r1573374 - /deltaspike/site/trunk/content/jsf.mdtext
Date Sun, 02 Mar 2014 21:44:59 GMT
Author: gpetracek
Date: Sun Mar  2 21:44:59 2014
New Revision: 1573374

URL: http://svn.apache.org/r1573374
Log:
updated content

Modified:
    deltaspike/site/trunk/content/jsf.mdtext

Modified: deltaspike/site/trunk/content/jsf.mdtext
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/jsf.mdtext?rev=1573374&r1=1573373&r2=1573374&view=diff
==============================================================================
--- deltaspike/site/trunk/content/jsf.mdtext (original)
+++ deltaspike/site/trunk/content/jsf.mdtext Sun Mar  2 21:44:59 2014
@@ -202,7 +202,7 @@ The window-scope is like a session per w
     }
 
 ## @ViewAccessScoped (since 0.6)
-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
@*View*AccessScoped.
+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 @*View*AccessScoped.
 
     :::java
     @ViewAccessScoped



Mime
View raw message