Author: buildbot
Date: Mon Feb 10 17:06:20 2014
New Revision: 897184

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 Mon Feb 10 17:06:20 2014
@@ -1 +1 @@
-1566681
+1566683

Modified: websites/staging/deltaspike/trunk/content/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/jsf.html Mon Feb 10 17:06:20 2014
@@ -185,7 +185,6 @@ In addition a cookie with with the dsRid
 <li>Every GET requests streams the the windowhandler.html first -&gt; The
     application probably feels a litte bit slower</li>
 </ul>
-<p><br/></p>
 <h4 id="change-windowhandlerhtml">Change windowhandler.html</h4>
 <p>To customize the look &amp; feel of the windowhandler.html, you can simply 
provide a own via:</p>
 <div class="codehilite"><pre><span class="nd">@Specializes</span>
@@ -215,7 +214,6 @@ If it's not matching, the view will be r
 <ul>
 <li>It could happen that 2 tabs will share the same windowId for 1 request 
because the <code>LAZY</code> mode will check lazily, after rendering the view, 
if the windowId matches the <code>window.name</code>. Therefore it could happen 
that @ViewAccessScoped or other scopes will unintentionally be destroyed. </li>
 </ul>
-<p><br/></p>
 <h4 id="workflow-example">Workflow example</h4>
 <h5 id="first-get-request-with-windowid">First GET request with windowId</h5>
 <ul>
@@ -240,18 +238,14 @@ If it's not matching, the view will be r
 <li>Renders the view</li>
 <li>If it does not match, reload the URL with the right windowId taken from 
<code>window.name</code></li>
 </ul>
-<p><br/></p>
 <h3 id="none">NONE</h3>
 <p>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.</p>
-<p><br/></p>
 <h3 id="delegated">DELEGATED</h3>
 <p>Delegates the complete window handling to thew new JSF 2.2 ClientWindow (if 
not disabled).</p>
-<p><br/></p>
 <h3 id="custom">CUSTOM</h3>
 <p>Enables to use an complete own 
<code>org.apache.deltaspike.jsf.spi.scope.window.ClientWindow</code> 
implementation.</p>
-<p><br/></p>
 <h2 id="configuration">Configuration</h2>
 <h3 id="dswindowid">ds:windowId</h3>
 <p>The component <code>ds:windowId</code> 
(<code>xmlns:ds="http://deltaspike.apache.org/jsf";</code>) is required to 
enable the full control of the DeltaSpike window handling.<br/>


Reply via email to