You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@deltaspike.apache.org by ta...@apache.org on 2015/11/25 23:05:32 UTC

deltaspike git commit: DELTASPIKE-1021 Enhance documentation for JSF module

Repository: deltaspike
Updated Branches:
  refs/heads/master dd223d480 -> a19d561de


DELTASPIKE-1021 Enhance documentation for JSF module

Project: http://git-wip-us.apache.org/repos/asf/deltaspike/repo
Commit: http://git-wip-us.apache.org/repos/asf/deltaspike/commit/a19d561d
Tree: http://git-wip-us.apache.org/repos/asf/deltaspike/tree/a19d561d
Diff: http://git-wip-us.apache.org/repos/asf/deltaspike/diff/a19d561d

Branch: refs/heads/master
Commit: a19d561de45ac1549b7c7c0c9adf13fd13462c6d
Parents: dd223d4
Author: Thomas Andraschko <ta...@apache.org>
Authored: Wed Nov 25 23:05:22 2015 +0100
Committer: Thomas Andraschko <ta...@apache.org>
Committed: Wed Nov 25 23:05:22 2015 +0100

----------------------------------------------------------------------
 documentation/src/main/asciidoc/jsf.adoc | 23 ++++++-----------------
 1 file changed, 6 insertions(+), 17 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/deltaspike/blob/a19d561d/documentation/src/main/asciidoc/jsf.adoc
----------------------------------------------------------------------
diff --git a/documentation/src/main/asciidoc/jsf.adoc b/documentation/src/main/asciidoc/jsf.adoc
index 31fc9a7..91fcf7e 100644
--- a/documentation/src/main/asciidoc/jsf.adoc
+++ b/documentation/src/main/asciidoc/jsf.adoc
@@ -153,7 +153,7 @@ bgcolor which matches your application. For html-5 aware browsers we
 also got rid of this flickering by storing away a 'screenshot' of the
 first page in onclick() and immediately restore this 'screenshot' on the
 intermediate windowhandler.html page. Technically we do this by storing
-away the and css information into the html5 localStorage and restore them on the
+away the HTML DOM tree and css information into the html5 localStorage and restore them on the
 intermediate page. We also introduced a WindowConfig which is able to
 parse a request and decide upon the UserAgent or any other information
 if a client will get an intermediate page or if he gets the result page
@@ -164,19 +164,13 @@ directly.
 ====== Reduce windowhandler.html flickering
 
 Per default we only overwrite the onclick events of all links on the current page to make a 'screenshot' between requests.
-We also provide a mechanism to store the 'screenshot' on ajax requests (e.g. Post-Redirect-Get via p:remoteCommand or other components) or on every button onclick:
+We also provide a mechanism to store the 'screenshot' on every button onclick:
 
 [source,java]
 ----------------------------------------------------------------------------
 @Specializes
 public class MyClientWindowConfig extends DefaultClientWindowConfig
-{
-    @Override
-    public boolean isClientWindowStoreWindowTreeEnabledOnAjaxRequest()
-    {
-        return true;
-    }
-    
+{    
     @Override
     public boolean isClientWindowStoreWindowTreeEnabledOnButtonClick()
     {
@@ -216,13 +210,7 @@ public class MyClientWindowConfig extends DefaultClientWindowConfig
     {
         return false;
     }
-    
-    @Override
-    public boolean isClientWindowStoreWindowTreeEnabledOnAjaxRequest()
-    {
-        return false;
-    }
-    
+
     @Override
     public boolean isClientWindowStoreWindowTreeEnabledOnButtonClick()
     {
@@ -272,7 +260,8 @@ the URL.
 * 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 `window.name`. Therefore it could happen that
-@ViewAccessScoped or other scopes will unintentionally be destroyed.
+scopes, which are based on the window handling (@ViewAccessScoped, @WindowScoped and @GroupedConversationScoped),
+will unintentionally be destroyed.
 
 
 ===== Workflow Example