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

[bu...@apache.org]

Author: buildbot
Date: Sun May 26 16:16:21 2013
New Revision: 863178

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 May 26 16:16:21 2013
@@ -1 +1 @@
-1486424
+1486426

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 May 26 16:16:21 2013
@@ -103,7 +103,11 @@
 <li><a href="#using-viewconfigresolver">Using ViewConfigResolver</a></li>
 </ul>
 </li>
-<li><a href="#advanced-api-usages">Advanced API usages</a></li>
+<li><a href="#advanced-api-usages">Advanced API usages</a><ul>
+<li><a href="#creating-custom-meta-data-via-viewmetadata">Creating Custom Meta-Data via @ViewMetaData</a></li>
+<li><a href="#creating-custom-callbacks-via-viewmetadata">Creating Custom Callbacks via @ViewMetaData</a></li>
+</ul>
+</li>
 <li><a href="#view-config-spi">View-Config SPI</a></li>
 <li><a href="#activation-of-custom-naming-conventions">Activation of custom naming conventions</a></li>
 </ul>
@@ -663,8 +667,8 @@ Furthermore, it's also possible to use i
 <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>
-<p>Creating Custom Meta-Data via @ViewMetaData
-This meta-annotation allows to create custom view-meta-data which can be used for view-configs. Per default meta-data of a lower level overrides meta-data on a higher level which has the same type. That can be customized via annotating the final annotation as a whole via <code>@Aggregated(true)</code>.</p>
+<h3 id="creating-custom-meta-data-via-viewmetadata">Creating Custom Meta-Data via @ViewMetaData</h3>
+<p>This meta-annotation allows to create custom view-meta-data which can be used for view-configs. Per default meta-data of a lower level overrides meta-data on a higher level which has the same type. That can be customized via annotating the final annotation as a whole via <code>@Aggregated(true)</code>.</p>
 <div class="codehilite"><pre><span class="nd">@ViewMetaData</span>
 <span class="nd">@interface</span> <span class="n">InfoPage</span>
 <span class="o">{</span>
@@ -682,7 +686,7 @@ This meta-annotation allows to create cu
 </pre></div>
 
 
-<p>Creating Custom Callbacks via @ViewMetaData</p>
+<h3 id="creating-custom-callbacks-via-viewmetadata">Creating Custom Callbacks via @ViewMetaData</h3>
 <p>Via a custom ConfigPreProcessor it's possible to register custom callbacks dynamically.
 The following listing shows a view-config which adds a simple callback including the corresponding <code>ConfigPreProcessor</code> and <code>ExecutableCallbackDescriptor</code>.</p>
 <div class="codehilite"><pre><span class="nd">@ViewMetaData</span><span class="o">(</span><span class="n">preProcessor</span> <span class="o">=</span> <span class="n">MySecured</span><span class="o">.</span><span class="na">AnnotationPreProcessor</span><span class="o">.</span><span class="na">class</span><span class="o">)</span>