svn commit: r856730 - in /websites/staging/deltaspike/trunk/content: ./ deltaspike/jsf.html

[bu...@apache.org]

Author: buildbot
Date: Sun Mar 31 14:36:08 2013
New Revision: 856730

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/deltaspike/jsf.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Mar 31 14:36:08 2013
@@ -1 +1 @@
-1462974
+1462975

Modified: websites/staging/deltaspike/trunk/content/deltaspike/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/deltaspike/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/deltaspike/jsf.html Sun Mar 31 14:36:08 2013
@@ -415,7 +415,7 @@ it won't be called for other pages).</p>
 However, also JSF supports manual navigation via <code>javax.faces.application.NavigationHandler</code>.
 With <code>ViewNavigationHandler</code> DeltaSpike provides an equivalent optimized for type-safe view-configs which is easier to use (and can be used also for other (supported) view technology).</p>
 <p>A simple example is:</p>
-<div class="codehilite"><pre><span class="kd">interface</span> <span class="nc">Pages</span> <span class="o">{</span>
+<div class="codehilite"><pre><span class="kd">public</span> <span class="kd">interface</span> <span class="nc">Pages</span> <span class="o">{</span>
     <span class="kd">class</span> <span class="nc">Index</span> <span class="kd">implements</span> <span class="n">ViewConfig</span> <span class="o">{</span> <span class="o">}</span>
 <span class="o">}</span>
 
@@ -439,7 +439,7 @@ With <code>ViewNavigationHandler</code> 
 <p>It's possible to mark one view-config class as default error-view. That means in case of errors it will be used as navigation target automatically.
 Furthermore, it's also possible to use it in your code instead of hardcoding your error-view across the whole application.</p>
 <p>In case of</p>
-<div class="codehilite"><pre><span class="kd">interface</span> <span class="nc">Pages</span> <span class="o">{</span>
+<div class="codehilite"><pre><span class="kd">public</span> <span class="kd">interface</span> <span class="nc">Pages</span> <span class="o">{</span>
     <span class="kd">class</span> <span class="nc">Index</span> <span class="kd">implements</span> <span class="n">ViewConfig</span> <span class="o">{</span> <span class="o">}</span>
 
     <span class="kd">class</span> <span class="nc">CustomErrorPage</span> <span class="kd">extends</span> <span class="n">DefaultErrorView</span> <span class="o">{</span> <span class="o">}</span>