Author: buildbot
Date: Sun Jul 7 15:36:20 2013
New Revision: 868717
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 Jul 7 15:36:20 2013
@@ -1 +1 @@
-1500426
+1500454
Modified: websites/staging/deltaspike/trunk/content/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/jsf.html Sun Jul 7 15:36:20 2013
@@ -109,7 +109,17 @@
<li><a
href="#creating-custom-inline-meta-data-via-inlineviewmetadata">Creating Custom
inline Meta-Data via @InlineViewMetaData</a></li>
</ul>
</li>
-<li><a href="#view-config-spi">View-Config SPI</a></li>
+<li><a href="#view-config-spi">View-Config SPI</a><ul>
+<li><a href="#configdescriptorvalidator">ConfigDescriptorValidator</a></li>
+<li><a href="#confignodeconverter">ConfigNodeConverter</a></li>
+<li><a href="#configpreprocessor">ConfigPreProcessor</a></li>
+<li><a href="#inlinemetadatatransformer">InlineMetaDataTransformer</a></li>
+<li><a href="#targetviewconfigprovider">TargetViewConfigProvider</a></li>
+<li><a
href="#viewconfiginheritancestrategy">ViewConfigInheritanceStrategy</a></li>
+<li><a href="#viewconfignode">ViewConfigNode</a></li>
+<li><a href="#viewconfigroot">@ViewConfigRoot</a></li>
+</ul>
+</li>
<li><a href="#activation-of-custom-naming-conventions">Activation of custom
naming conventions</a></li>
</ul>
</li>
@@ -740,6 +750,30 @@ The following listing shows a view-confi
Via a <code>TargetViewConfigProvider</code> it's possible to point to the
view-config the meta-data should get applied to and via
<code>InlineMetaDataTransformer</code> it's possible to convert it to a
different meta-data-representation (which allows that at runtime you only have
to support one side since the inline-meta-data was converted to the same
meta-data representation which is used for the normal view-meta-data).</p>
<h2 id="view-config-spi">View-Config SPI</h2>
<p>[TODO]</p>
+<h3 id="configdescriptorvalidator">ConfigDescriptorValidator</h3>
+<p>Allows to validate the final view-config descriptors before they get
deployed.
+Since the config-descriptor contains e.g. the final path, it's also possible
to validate if the corresponding file exists.
+Use <code>ViewConfigRoot</code> to configure 1-n validators.</p>
+<h3 id="confignodeconverter">ConfigNodeConverter</h3>
+<p>Allows to provide custom strategies to process the nodes of the built
config-tree.
+Use <code>ViewConfigRoot</code> to configure a custom converter.</p>
+<h3 id="configpreprocessor">ConfigPreProcessor</h3>
+<p>Allows to change the found meta-data (e.g. replace default values,
callbacks,...) or the <code>ViewConfigNode</code> itself.</p>
+<h3 id="inlinemetadatatransformer">InlineMetaDataTransformer</h3>
+<p>Allows to transform an annotation annotated with @InlineViewMetaData to an
annotation annotated with @ViewMetaData.
+This transformer is optional and only needed if it should result in the same
at runtime, but the inline-meta-data needs a different syntax via a different
annotation (compared to the view-config meta-data).
+See e.g. <code>@ViewRef</code> vs. <code>@ViewControllerRef</code>.</p>
+<h3 id="targetviewconfigprovider">TargetViewConfigProvider</h3>
+<p>Allows to provide a custom reference to <code>ViewConfig</code> classes
(see e.g. <code>@InlineViewMetaData</code> and <code>@ViewRef</code>)</p>
+<h3 id="viewconfiginheritancestrategy">ViewConfigInheritanceStrategy</h3>
+<p>Allows to customize the inheritance-strategy for meta-data.
+E.g. inheritance via std. java inheritance vs. inheritance via nested
interfaces.
+Use <code>ViewConfigRoot</code> to configure a custom inheritance-strategy.</p>
+<h3 id="viewconfignode">ViewConfigNode</h3>
+<p>Node-type used for building the meta-data-tree during the bootstrapping
process.</p>
+<h3 id="viewconfigroot">@ViewConfigRoot</h3>
+<p>Optional annotation which allows to provide custom implementations.
+Only annotate one <code>ViewConfig</code> class which represents the root
node.</p>
<h2 id="activation-of-custom-naming-conventions">Activation of custom naming
conventions</h2>
<p>DeltaSpike allows to customize the default naming convention via
<code>View.DefaultBasePathBuilder</code> and/or
<code>View.DefaultFileNameBuilder</code> and/or
<code>View.DefaultExtensionBuilder</code>.
It's possible to change it for one usage via <code>View.basePathBuilder</code>
and/or <code>View.fileNameBuilder</code> and/or
<code>View.extensionBuilder</code> or globally via the config mechanism
provided by DeltaSpike.
