Author: buildbot
Date: Sun Jul 7 15:38:48 2013
New Revision: 868718
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:38:48 2013
@@ -1 +1 @@
-1500454
+1500457
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:38:48 2013
@@ -760,7 +760,7 @@ Use <code>ViewConfigRoot</code> to confi
<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.
+<p>Allows to transform an annotation annotated with
<code>@InlineViewMetaData</code> to an annotation annotated with
<code>@ViewMetaData</code>.
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>
