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

[bu...@apache.org]

Author: buildbot
Date: Fri Mar 22 23:54:54 2013
New Revision: 855630

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 Fri Mar 22 23:54:54 2013
@@ -1 +1 @@
-1460056
+1460060

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 Fri Mar 22 23:54:54 2013
@@ -108,9 +108,9 @@ In case of JSF you can use it for naviga
 </pre></div>
 
 
-<p>This leads to a forward to /myPage.xhtml. Information like base-path, file- (and folder-)name/s, file-extension, navigation mode, view-params,... can be customized with the corresponding (meta-data-)annotations.
-One of those annotations provided by the JSF module (which is optional) is @View. That means the following example leads to the same as the first one.</p>
-<div class="codehilite"><pre><span class="nd">@View</span>
+<p>This leads to a forward to <code>/myPage.xhtml</code>. Information like base-path, file- (and folder-)name/s, file-extension, navigation mode, view-params,... can be customized with the corresponding (meta-data-)annotations.
+One of those annotations provided by the JSF module (which is optional) is <code>@View</code>. That means the following example leads to the same as the first one.</p>
+<div class="codehilite"><pre><span class="nd">@View</span> <span class="c1">//optional</span>
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">MyPage</span> <span class="kd">implements</span> <span class="n">ViewConfig</span>
 <span class="o">{</span>
 <span class="o">}</span>
@@ -133,9 +133,9 @@ One of those annotations provided by the
 <p>In case of the JSF integration it leads to the following view-ids:<br/>
 /pages/index.xhtml<br/>
 /pages/adminArea/index.xhtml<br/></p>
-<p>Like the optional @View for pages represented by the classes, it's possible to use the optional @Folder annotation for directories represented by the (nested) interfaces.</p>
+<p>Like the optional <code>@View</code> for pages represented by the classes, it's possible to use the optional <code>@Folder</code> annotation for directories represented by the (nested) interfaces.</p>
 <p>Furthermore, it's possible to inherit meta-data along with the normal inheritance.</p>
-<p>In the following example Pages.Admin.Index, Pages.Admin.Home and Pages.Admin.Statistics.Home inherit the meta-data from Pages.Admin because they implement the interface whereas Pages.Admin.Statistics.Index doesn't. However, Pages.Admin.Home overrides View#navigation. During the bootstrapping process the meta-data gets merged and at runtime you only see the final result (which is cached).</p>
+<p>In the following example <code>Pages.Admin.Index</code>, <code>Pages.Admin.Home</code> and <code>Pages.Admin.Statistics.Home</code> inherit the meta-data from <code>Pages.Admin</code> because they implement the interface whereas <code>Pages.Admin.Statistics.Index</code> doesn't. However, Pages.Admin.Home overrides View#navigation. During the bootstrapping process the meta-data gets merged and at runtime you only see the final result (which is cached).</p>
 <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="nd">@View</span><span class="o">(</span><span class="n">name</span> <span class="o">=</span> <span class="s">&quot;home&quot;</span><span class="o">,</span> <span class="n">extension</span> <span class="o">=</span> <span class="n">JSP</span><span class="o">)</span>
@@ -161,7 +161,7 @@ One of those annotations provided by the
 </pre></div>
 
 
-<p>In this case Pages.Admin.Statistics is just an interface to reflect the folder structure. For sure it's also possible that it extends an existing view-config interface and other folders and/or pages inherit its meta-data (like Pages.Admin).</p>
+<p>In this case <code>Pages.Admin.Statistics</code> is just an interface to reflect the folder structure. For sure it's also possible that it extends an existing view-config interface and other folders and/or pages inherit its meta-data (like <code>Pages.Admin</code>).</p>
 <p>Furthermore, inheritance can be used to ensure navigation to the correct area in the application. In the following example the return type of the action-method (and therefore the compiler of Java) ensures that the navigation target of this method is within the admin-area.</p>
 <div class="codehilite"><pre><span class="kd">public</span> <span class="n">Class</span><span class="o">&lt;?</span> <span class="kd">extends</span> <span class="n">Pages</span><span class="o">.</span><span class="na">Admin</span><span class="o">&gt;</span> <span class="n">toNextPage</span><span class="o">()</span>
 <span class="o">{</span>
@@ -180,8 +180,8 @@ One of those annotations provided by the
 <p>[TODO]</p>
 <h3 id="security-integration-via-secured">Security Integration via @Secured</h3>
 <p>This annotation is a custom view-meta-data provided by the Security-module which allows to integrate 3rd party frameworks (or custom approaches) to secure pages as well as whole folders.
-You can annotate specific parts or a marker-interface. CustomAccessDecisionVoter used in the following example can be any implementation of org.apache.deltaspike.security.api.authorization.AccessDecisionVoter.
-All parts which inherit from SecuredPages (Pages.Admin, Pages.Admin.Index and Pages.Admin.Home) are protected by CustomAccessDecisionVoter.<br/></p>
+You can annotate specific parts or a marker-interface. <code>CustomAccessDecisionVoter</code> used in the following example can be any implementation of <code>org.apache.deltaspike.security.api.authorization.AccessDecisionVoter</code>.
+All parts which inherit from <code>SecuredPages</code> (<code>Pages.Admin</code>, <code>Pages.Admin.Index</code> and <code>Pages.Admin.Home</code>) are protected by <code>CustomAccessDecisionVoter</code>.<br/></p>
 <p>(It's easy to check this hierarchy in a modern Java-IDE. Only for displaying the final meta-data for every node in the IDE a special plug-in would be needed.)</p>
 <div class="codehilite"><pre><span class="nd">@Secured</span><span class="o">(</span><span class="n">CustomAccessDecisionVoter</span><span class="o">.</span><span class="na">class</span><span class="o">)</span>
 <span class="kd">public</span> <span class="kd">interface</span> <span class="nc">SecuredPages</span> <span class="o">{}</span>
@@ -240,7 +240,7 @@ All parts which inherit from SecuredPage
 
 
 <h3 id="view-controller-callbacks-via-viewcontrollerbean">View-Controller Callbacks via @ViewControllerBean</h3>
-<p>This annotation is a custom view-meta-data provided by the JSF-module which allows to configure beans which should act as view-controllers. That means they can use view-controller callbacks like @InitView, @PreViewAction, @PreRenderView and @PostRenderView. The following example shows the usage of @PreRenderView.</p>
+<p>This annotation is a custom view-meta-data provided by the JSF-module which allows to configure beans which should act as view-controllers. That means they can use view-controller callbacks like <code>@InitView</code>, <code>@PreViewAction</code>, <code>@PreRenderView</code> and <code>@PostRenderView</code>. The following example shows the usage of <code>@PreRenderView</code>.</p>
 <div class="codehilite"><pre><span class="c1">//@View //optional</span>
 <span class="nd">@ViewControllerBean</span><span class="o">(</span><span class="n">MyPageController</span><span class="o">.</span><span class="na">class</span><span class="o">)</span>
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">MyPage</span> <span class="kd">implements</span> <span class="n">ViewConfig</span>