Author: tandraschko
Date: Sat Feb 15 11:58:30 2014
New Revision: 1568620
URL: http://svn.apache.org/r1568620
Log:
cosmetics
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=1568620&r1=1568619&r2=1568620&view=diff
==============================================================================
--- deltaspike/site/trunk/content/jsf.mdtext (original)
+++ deltaspike/site/trunk/content/jsf.mdtext Sat Feb 15 11:58:30 2014
@@ -180,7 +180,7 @@ Don't forget to set the ClientWindowRend
- @ViewAccessScoped
- @GroupedConversationScoped
-#Scopes (TODO)
+#Scopes
## @WindowScoped
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.
@@ -192,7 +192,7 @@ The window-scope is like a session per w
//...
}
-## @ViewAccessScoped
+## @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.
:::java
@@ -206,7 +206,7 @@ Hint: <br/>
@ViewAccessScoped beans are best used in conjunction with the `CLIENTWINDOW`
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.
-## @GroupedConversationScoped
+## @GroupedConversationScoped (since 0.6)
See <a href="#grouped-conversations">(Grouped-)Conversations</a>
## @ViewScoped
