deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r915285 - in /websites/staging/deltaspike/trunk/content: ./ jsf.html
Date Sun, 06 Jul 2014 18:36:13 GMT
Author: buildbot
Date: Sun Jul  6 18:36:13 2014
New Revision: 915285

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  6 18:36:13 2014
@@ -1 +1 @@
-1608015
+1608277

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  6 18:36:13 2014
@@ -1130,6 +1130,7 @@ Use <code>@ViewConfigRoot</code> to conf
 <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>
+<p>If you are using CDI 1.1+ with bean-discovery-mode <code>annotated</code>,
you can use <code>@ViewConfigRoot</code> in combination with <code>@ApplicationScoped</code>
as marker annotations. Since DeltaSpike 1.0.1 this combination allows to add all nested interfaces
and classes and therefore no additional annotations (required by bean-discovery-mode <code>annotated</code>)
are needed.</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.



Mime
View raw message