Author: buildbot
Date: Thu Dec 10 00:02:15 2015
New Revision: 975129
Log:
Staging update by buildbot for deltaspike
Modified:
websites/staging/deltaspike/trunk/content/ (props changed)
websites/staging/deltaspike/trunk/content/documentation/build.html
websites/staging/deltaspike/trunk/content/documentation/configure.html
websites/staging/deltaspike/trunk/content/documentation/jsf.html
websites/staging/deltaspike/trunk/content/documentation/scheduler.html
websites/staging/deltaspike/trunk/content/documentation/snapshots.html
Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Dec 10 00:02:15 2015
@@ -1 +1 @@
-1718991
+1718992
Modified: websites/staging/deltaspike/trunk/content/documentation/build.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/build.html
(original)
+++ websites/staging/deltaspike/trunk/content/documentation/build.html Thu Dec
10 00:02:15 2015
@@ -277,7 +277,7 @@ table.CodeRay td.code>pre{padding:0}
<p>The DeltaSpike source (modules and examples) is provided for inspection,
contribution and testing purposes. The source must be built with Maven, which
has been used to automate the compilation, testing and packaging processes.
Arquillian tests are included with the source and a CDI implementation or
container can be specified with which to carry out the tests.</p>
</div>
<div class="paragraph">
-<p>In all cases, to obtain the DeltaSpike source, <a
href="https://deltaspike.apache.org/download.html";>download</a>
<code>deltaspike-project-1.5.1-source-release.zip</code> and extract the
contents.</p>
+<p>In all cases, to obtain the DeltaSpike source, <a
href="https://deltaspike.apache.org/download.html";>download</a>
<code>deltaspike-project-1.5.2-source-release.zip</code> and extract the
contents.</p>
</div>
<div class="admonitionblock note">
<table>
@@ -301,7 +301,7 @@ You can also obtain the DeltaSpike sourc
</div>
<div class="listingblock">
<div class="content">
-<pre class="CodeRay highlight"><code data-lang="shell">$ cd
/path/to/deltaspike-project-1.5.1/
+<pre class="CodeRay highlight"><code data-lang="shell">$ cd
/path/to/deltaspike-project-1.5.2/
$ mvn clean install</code></pre>
</div>
</div>
Modified: websites/staging/deltaspike/trunk/content/documentation/configure.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/configure.html
(original)
+++ websites/staging/deltaspike/trunk/content/documentation/configure.html Thu
Dec 10 00:02:15 2015
@@ -309,7 +309,7 @@ You can also opt to use the lastest Delt
<div class="listingblock">
<div class="content">
<pre class="CodeRay highlight"><code data-lang="xml"><span
class="tag"><properties></span>
- <span class="tag"><deltaspike.version></span>1.5.1<span
class="tag"></deltaspike.version></span>
+ <span class="tag"><deltaspike.version></span>1.5.2<span
class="tag"></deltaspike.version></span>
<span class="tag"></properties></span></code></pre>
</div>
</div>
Modified: websites/staging/deltaspike/trunk/content/documentation/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/documentation/jsf.html Thu Dec 10
00:02:15 2015
@@ -434,9 +434,11 @@ not feasible as general solution.</p>
<div class="sect3">
<h4 id="_clientwindow">CLIENTWINDOW</h4>
<div class="paragraph">
-<p>Each GET request results in an intermediate small html page which checks
-if the browser tab fits the requested windowId. When the windowId is
-valid, a unique token (called <code>dsrid</code>) will be generated for the
current
+<p>Each GET request results in an intermediate small HTML page (aka
"windowhandler").
+If the window.name is empty, a new windowId will stored into window.name.
+If the window.name is already set, the windowhandler checks if the
+window.name equals the requested windowId. When the windowId is valid, a unique
+token (called <code>dsrid</code>) will be generated for the current
request and added to the URL. In addition a cookie with with the
dsrid/dswid will be added. On the server side, the verified windowId
will be extracted from the cookie. For POST request detection, the
@@ -466,7 +468,7 @@ bgcolor which matches your application.
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
@@ -481,7 +483,7 @@ directly.</p>
<h6 id="_reduce_windowhandler_html_flickering">Reduce windowhandler.html
flickering</h6>
<div class="paragraph">
<p>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:</p>
+We also provide a mechanism to store the 'screenshot' on every button
onclick:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -489,12 +491,6 @@ We also provide a mechanism to store the
<span class="directive">public</span> <span class="type">class</span> <span
class="class">MyClientWindowConfig</span> <span
class="directive">extends</span> DefaultClientWindowConfig
{
<span class="annotation">@Override</span>
- <span class="directive">public</span> <span class="type">boolean</span>
isClientWindowStoreWindowTreeEnabledOnAjaxRequest()
- {
- <span class="keyword">return</span> <span
class="predefined-constant">true</span>;
- }
-
- <span class="annotation">@Override</span>
<span class="directive">public</span> <span class="type">boolean</span>
isClientWindowStoreWindowTreeEnabledOnButtonClick()
{
<span class="keyword">return</span> <span
class="predefined-constant">true</span>;
@@ -538,12 +534,6 @@ if you would like to always show your cu
}
<span class="annotation">@Override</span>
- <span class="directive">public</span> <span class="type">boolean</span>
isClientWindowStoreWindowTreeEnabledOnAjaxRequest()
- {
- <span class="keyword">return</span> <span
class="predefined-constant">false</span>;
- }
-
- <span class="annotation">@Override</span>
<span class="directive">public</span> <span class="type">boolean</span>
isClientWindowStoreWindowTreeEnabledOnButtonClick()
{
<span class="keyword">return</span> <span
class="predefined-constant">false</span>;
@@ -607,7 +597,8 @@ the URL.</p>
<p>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.</p>
+scopes, which are based on the window handling (@ViewAccessScoped,
@WindowScoped and @GroupedConversationScoped),
+will unintentionally be destroyed.</p>
</li>
</ul>
</div>
Modified: websites/staging/deltaspike/trunk/content/documentation/scheduler.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/scheduler.html
(original)
+++ websites/staging/deltaspike/trunk/content/documentation/scheduler.html Thu
Dec 10 00:02:15 2015
@@ -476,7 +476,7 @@ start a job once (without registering it
<div class="sectionbody">
<div class="paragraph">
<p>It is possible to replace the default integration with Quartz. Any
scheduler that supports cron-expressions for job-classes can be used.
-For more information, see <a
href="https://deltaspike.apache.org/javadoc/1.5.1/org/apache/deltaspike/scheduler/spi/Scheduler.html";>Scheduler
javadoc</a>.</p>
+For more information, see <a
href="https://deltaspike.apache.org/javadoc/1.5.2/org/apache/deltaspike/scheduler/spi/Scheduler.html";>Scheduler
javadoc</a>.</p>
</div>
</div>
</div>
Modified: websites/staging/deltaspike/trunk/content/documentation/snapshots.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/snapshots.html
(original)
+++ websites/staging/deltaspike/trunk/content/documentation/snapshots.html Thu
Dec 10 00:02:15 2015
@@ -343,7 +343,7 @@ Snapshots provide previews of DeltaSpike
<div class="listingblock">
<div class="content">
<pre class="CodeRay highlight"><code data-lang="xml"><span
class="tag"><properties></span>
- <span class="tag"><deltaspike.version></span>1.5.2-SNAPSHOT<span
class="tag"></deltaspike.version></span>
+ <span class="tag"><deltaspike.version></span>1.5.3-SNAPSHOT<span
class="tag"></deltaspike.version></span>
<span class="tag"></properties></span></code></pre>
</div>
</div>
