Author: buildbot
Date: Sun Jul 6 18:42:19 2014
New Revision: 915289
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:42:19 2014
@@ -1 +1 @@
-1608277
+1608281
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:42:19 2014
@@ -133,6 +133,7 @@
<li><a href="#type-safe-view-configs">Type-safe View-Configs</a><ul>
<li><a href="#intro_1">Intro</a></li>
<li><a href="#motivation">Motivation</a></li>
+<li><a href="#bean-discovery-mode-annotated">Bean-discovery-mode
annotated</a></li>
<li><a href="#basic-api-usages">Basic API usages</a><ul>
<li><a href="#file-view-and-folder-folder-paths">File (@View) and Folder
(@Folder) paths</a><ul>
<li><a href="#foldername">@Folder#name</a></li>
@@ -482,6 +483,8 @@ So why should you use something which is
<li>It's possible to validate the config (if the corresponding path (view or
folder) really exists (after v0.5 it's done out-of-the-box)</li>
</ul>
<p>If you are still not convinced, you just have to try it. You will see how
your daily workflow benefits from it pretty soon.</p>
+<h2 id="bean-discovery-mode-annotated">Bean-discovery-mode annotated</h2>
+<p>CDI 1.1 introduced a concept called bean-discovery-mode. If you would like
to use the mode <code>annotated</code>, please have a look at the hint at <a
href="#viewconfigroot">@ViewConfigRoot</a></p>
<h2 id="basic-api-usages">Basic API usages</h2>
<p>While reading this section keep the following simple rules in mind:
<ul>
