You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@deltaspike.apache.org by bu...@apache.org on 2013/03/31 22:24:20 UTC

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

Author: buildbot
Date: Sun Mar 31 20:24:20 2013
New Revision: 856782

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 20:24:20 2013
@@ -1 +1 @@
-1463040
+1463048

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 20:24:20 2013
@@ -494,12 +494,12 @@ Furthermore, it's also possible to use i
 
     <span class="kd">public</span> <span class="n">String</span> <span class="nf">getViewId</span><span class="o">(</span><span class="n">Class</span><span class="o">&lt;?</span> <span class="kd">extends</span> <span class="n">ViewConfig</span><span class="o">&gt;</span> <span class="n">viewConfigClass</span><span class="o">)</span>
     <span class="o">{</span>
-        <span class="k">return</span> <span class="n">viewConfigResolver</span><span class="o">.</span><span class="na">getViewConfigDescriptor</span><span class="o">(</span><span class="n">viewConfigClass</span><span class="o">).</span><span class="na">getViewId</span><span class="o">();</span> <span class="c1">//or #toString</span>
+        <span class="k">return</span> <span class="n">viewConfigResolver</span><span class="o">.</span><span class="na">getViewConfigDescriptor</span><span class="o">(</span><span class="n">viewConfigClass</span><span class="o">).</span><span class="na">getViewId</span><span class="o">();</span> <span class="c1">//or #getPath</span>
     <span class="o">}</span>
 
     <span class="kd">public</span> <span class="n">String</span> <span class="nf">getPath</span><span class="o">(</span><span class="n">Class</span> <span class="n">pathConfigClass</span><span class="o">)</span>
     <span class="o">{</span>
-        <span class="k">return</span> <span class="n">viewConfigResolver</span><span class="o">.</span><span class="na">getConfigDescriptor</span><span class="o">(</span><span class="n">pathConfigClass</span><span class="o">).</span><span class="na">toString</span><span class="o">();</span>
+        <span class="k">return</span> <span class="n">viewConfigResolver</span><span class="o">.</span><span class="na">getConfigDescriptor</span><span class="o">(</span><span class="n">pathConfigClass</span><span class="o">).</span><span class="na">getPath</span><span class="o">();</span>
     <span class="o">}</span>
 
     <span class="kd">public</span> <span class="n">List</span><span class="o">&lt;</span><span class="n">ConfigDescriptor</span><span class="o">&lt;?&gt;&gt;</span> <span class="n">getAllFolderDescriptors</span><span class="o">()</span>
@@ -528,7 +528,7 @@ Furthermore, it's also possible to use i
 
 <p>For folders it's optional to implement the <code>ViewConfig</code> interface, therefore you see 2 different types of API.
 <code>#getConfigDescriptor</code> as the general API and <code>#getViewConfigDescriptor</code> which is specific for pages (which have to implement the <code>ViewConfig</code> interface).</p>
-<p><strong>Besides</strong> translating a config class to the final path of the folder or page, it's possible to get the implicitly as well as explicitly configured (view-)meta-data, get and/or execute configured callbacks</p>
+<p><strong>Besides</strong> translating a config class to the final path of the folder or page, it's possible to get the implicitly as well as explicitly configured (view-)meta-data and get and/or execute configured callbacks.</p>
 <h2 id="advanced-api-usages">Advanced API usages</h2>
 <p>[TODO]</p>
 <h3 id="creating-custom-meta-data-via-viewmetadata">Creating Custom Meta-Data via @ViewMetaData</h3>