deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1566683 - /deltaspike/site/trunk/content/jsf.mdtext
Date Mon, 10 Feb 2014 17:06:15 GMT
Author: tandraschko
Date: Mon Feb 10 17:06:15 2014
New Revision: 1566683

Further work on window handling...


Modified: deltaspike/site/trunk/content/jsf.mdtext
--- deltaspike/site/trunk/content/jsf.mdtext (original)
+++ deltaspike/site/trunk/content/jsf.mdtext Mon Feb 10 17:06:15 2014
@@ -41,7 +41,6 @@ In addition a cookie with with the dsRid
   - Every GET requests streams the the windowhandler.html first -> The
     application probably feels a litte bit slower
 #### Change windowhandler.html
 To customize the look & feel of the windowhandler.html, you can simply provide a own
@@ -74,7 +73,6 @@ If it's not matching, the view will be r
   - It could happen that 2 tabs will share the same windowId for 1 request because the `LAZY`
mode will check lazily, after rendering the view, if the windowId matches the ``.
Therefore it could happen that @ViewAccessScoped or other scopes will unintentionally be destroyed.

 #### Workflow example
 ##### First GET request with windowId
@@ -96,24 +94,20 @@ If it's not matching, the view will be r
   - Renders the view
   - If it does not match, reload the URL with the right windowId taken from ``
 ### NONE
 Any window or browser tab detection will be disabled for the current request.<br/>
 Scopes like @WindowScoped, @GroupedConversationScoped or @ViewAccessScoped will not work.
 This is also the default mode if the current request doesn't support Javascript or if the
user agent is a bot/crawler.
 Delegates the complete window handling to thew new JSF 2.2 ClientWindow (if not disabled).
 Enables to use an complete own `org.apache.deltaspike.jsf.spi.scope.window.ClientWindow`
 ## Configuration
 ### ds:windowId

View raw message