Author: buildbot
Date: Sun Jan  5 22:26:00 2014
New Revision: 892909

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 Sun Jan  5 22:26:00 2014
@@ -1 +1 @@
-1555641
+1555642

Modified: websites/staging/deltaspike/trunk/content/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/jsf.html Sun Jan  5 22:26:00 2014
@@ -988,7 +988,7 @@ If you have an use-case (e.g. a wizard) 
 
 
 <p>Hint:
-DeltaSpike conversations get closed/restarted immediately instead of keeping 
them until the end of the request like std. conversations do, because the 
behaviour of std. conversations breaks a lot of use-cases. However, if you 
really need to keep them until the end of the request, you can close them in a 
@PostRenderView callback.</p>
+DeltaSpike conversations get closed/restarted immediately instead of keeping 
them until the end of the request like std. conversations do, because the 
behaviour of std. conversations breaks a lot of use-cases. However, if you 
really need to keep them until the end of the request, you can close them in a 
<code>@PostRenderView</code> callback.</p>
 <h1 id="support-of-ear-deployments">Support of EAR deployments</h1>
 <p>Before using features described by this page, please ensure that you are 
aware of <a 
href="https://issues.apache.org/jira/browse/DELTASPIKE-335";>DELTASPIKE-335</a> 
and the corresponding impact.</p>
 <h1 id="hints">Hints</h1>


Reply via email to