deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rsme...@apache.org
Subject svn commit: r1679029 [1/2] - in /deltaspike/site/trunk/content/documentation: bean-validation.html container-control.html data.html jpa.html jsf.html partial-bean.html scheduler.html security.html servlet.html test-control.html
Date Tue, 12 May 2015 18:37:06 GMT
Author: rsmeral
Date: Tue May 12 18:37:06 2015
New Revision: 1679029

URL: http://svn.apache.org/r1679029
Log:
Site checkin for project Apache DeltaSpike Documentation

Modified:
    deltaspike/site/trunk/content/documentation/bean-validation.html
    deltaspike/site/trunk/content/documentation/container-control.html
    deltaspike/site/trunk/content/documentation/data.html
    deltaspike/site/trunk/content/documentation/jpa.html
    deltaspike/site/trunk/content/documentation/jsf.html
    deltaspike/site/trunk/content/documentation/partial-bean.html
    deltaspike/site/trunk/content/documentation/scheduler.html
    deltaspike/site/trunk/content/documentation/security.html
    deltaspike/site/trunk/content/documentation/servlet.html
    deltaspike/site/trunk/content/documentation/test-control.html

Modified: deltaspike/site/trunk/content/documentation/bean-validation.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/bean-validation.html?rev=1679029&r1=1679028&r2=1679029&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/bean-validation.html (original)
+++ deltaspike/site/trunk/content/documentation/bean-validation.html Tue May 12 18:37:06 2015
@@ -281,7 +281,7 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>. For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure DeltaSpike in Maven-independent Projects</a>.</p>
@@ -305,10 +305,8 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
+<h2 id="_scoping">Scoping</h2>
 <div class="sectionbody">
-<div class="sect2">
-<h3 id="_scoping">Scoping</h3>
 <div class="paragraph">
 <p>A <code>ConstraintValidator</code> inherits the scope defined in the bean class.</p>
 </div>
@@ -325,8 +323,10 @@ A <code>ConstraintValidator</code> may b
 </table>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_code_requirements">Code Requirements</h3>
+</div>
+<div class="sect1">
+<h2 id="_code_requirements">Code Requirements</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>There are no compile dependencies to use the Bean Validation module. You
 simply need to override the factory. Then you can build your <code>ConstraintValidator</code> based on CDI programming rules.</p>
@@ -349,7 +349,6 @@ simply need to override the factory. The
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -375,18 +374,14 @@ simply need to override the factory. The
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_declare_bean_validation_module_dependencies">Declare Bean Validation Module Dependencies</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#_scoping">Scoping</a></li>
 <li><a href="#_code_requirements">Code Requirements</a></li>
 </ul>
-</li>
-</ul>
                     </div>
                 
             </div>

Modified: deltaspike/site/trunk/content/documentation/container-control.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/container-control.html?rev=1679029&r1=1679028&r2=1679029&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/container-control.html (original)
+++ deltaspike/site/trunk/content/documentation/container-control.html Tue May 12 18:37:06 2015
@@ -281,7 +281,7 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>. For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure DeltaSpike in Maven-independent Projects</a>.</p>
@@ -311,10 +311,8 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
+<h2 id="_start_the_cdi_container_from_your_project">Start the CDI Container from Your Project</h2>
 <div class="sectionbody">
-<div class="sect2">
-<h3 id="_start_the_cdi_container_from_your_project">Start the CDI Container from Your Project</h3>
 <div class="paragraph">
 <p>To start a CDI container in your application, you must instantiate a <code>CdiContainer</code> object and call the <code>#boot</code> method. When <code>#boot</code> is called, the <code>CdiContainer</code> scans CDI-enabled
 archives for beans and CDI extensions. Before the application exits, <code>#shutdown</code> must be called to correctly destroy all beans. An example is given in the code snippet here.</p>
@@ -373,8 +371,10 @@ archives for beans and CDI extensions. B
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_cdicontainer">CdiContainer</h3>
+</div>
+<div class="sect1">
+<h2 id="_cdicontainer">CdiContainer</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>The <code>CdiContainer</code> interface provides booting and shutdown of the CDI containers from deployed applications, with <code>CdiContainerLoader</code> a simple factory providing access to the underlying <code>CdiContainer</code> implementation.</p>
 </div>
@@ -385,14 +385,18 @@ archives for beans and CDI extensions. B
 <p>For instructions and examples on using this feature in your projects, see <a href="cdiimp.html#javase6">Enable CDI For Your Java Environment: Java SE6+</a>.</p>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_contextcontrol_usage">ContextControl Usage</h3>
+</div>
+<div class="sect1">
+<h2 id="_contextcontrol_usage">ContextControl Usage</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>The <code>ContextControl</code> interface provides life-cycle control of the CDI container built-in contexts. This includes starting and stoping built-in standard contexts like <code>@RequestScoped</code>, <code>@ConversationScoped</code>, and <code>@SessionScoped</code>. It is provided as an <code>@Dependent</code> bean and can be injected in the classic CDI way. This feature can be used and is helpful in all Java environments, including Java SE, as illustrated here.</p>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_procedure_for_builing_uber_jar">Procedure for builing Uber jar</h3>
+</div>
+<div class="sect1">
+<h2 id="_procedure_for_building_an_uber_jar">Procedure for building an uber jar</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Uber jar or executable jar can created by using the maven shade plugin. Some things you needs to be aware of when you use it.</p>
 </div>
@@ -418,8 +422,8 @@ archives for beans and CDI extensions. B
 </li>
 </ul>
 </div>
-<div class="sect3">
-<h4 id="_restart_the_requestcontext_in_unit_tests">Restart the RequestContext in Unit Tests</h4>
+<div class="sect2">
+<h3 id="_restart_the_requestcontext_in_unit_tests">Restart the RequestContext in Unit Tests</h3>
 <div class="paragraph">
 <p>In unit testing it can be necessary to test with attached and also with
 detached JPA entities. A very common approach for JPA is the
@@ -451,8 +455,8 @@ EntityManager. Since a single unit test
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_attach_a_requestcontext_to_a_new_thread_in_ee">Attach a RequestContext to a New Thread in EE</h4>
+<div class="sect2">
+<h3 id="_attach_a_requestcontext_to_a_new_thread_in_ee">Attach a RequestContext to a New Thread in EE</h3>
 <div class="paragraph">
 <p>Accessing the <code>@RequestScoped</code> bean in a new thread will result in a
 <code>ContextNotActiveException</code>. The RequestContext usually gets started
@@ -488,8 +492,10 @@ business services in for example a Quart
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_embedded_servlet_support">Embedded Servlet Support</h3>
+</div>
+<div class="sect1">
+<h2 id="_embedded_servlet_support">Embedded Servlet Support</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>From DeltaSpike 1.0.2, you can use DeltaSpike to power embedded Servlet
 runtimes. This work is done via Servlet Listeners. The configuration is
@@ -515,8 +521,8 @@ cdiContainer.boot();
 cdiContainer.getContextControl().startContexts();</code></pre>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_jetty">Jetty</h4>
+<div class="sect2">
+<h3 id="_jetty">Jetty</h3>
 <div class="paragraph">
 <p>For Jetty, you need to add an <code>EventListener</code> which will be your
 <code>CdiServletRequestListener</code>. The object must be instantiated. This must
@@ -536,8 +542,8 @@ server.start();</code></pre>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_undertow">Undertow</h4>
+<div class="sect2">
+<h3 id="_undertow">Undertow</h3>
 <div class="paragraph">
 <p>For Undertow, you register the <code>CdiServletRequestListener</code> via
 <code>ListenerInfo</code> by passing in the class to their builders. Then you add
@@ -563,8 +569,8 @@ server.start();</code></pre>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_tomcat">Tomcat</h4>
+<div class="sect2">
+<h3 id="_tomcat">Tomcat</h3>
 <div class="paragraph">
 <p>For Tomcat, you need to register the <code>CdiServletContextListener</code> instead
 of the <code>CdiServletRequestListener</code>. It is added as an
@@ -586,7 +592,6 @@ tomcat.start();</code></pre>
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -605,33 +610,29 @@ tomcat.start();</code></pre>
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_enable_cdi_for_your_java_environment">Enable CDI For Your Java Environment</a></li>
 <li><a href="#_declare_container_control_module_dependencies">Declare Container Control Module Dependencies</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#_start_the_cdi_container_from_your_project">Start the CDI Container from Your Project</a></li>
 <li><a href="#_cdicontainer">CdiContainer</a></li>
 <li><a href="#_contextcontrol_usage">ContextControl Usage</a></li>
-<li><a href="#_procedure_for_builing_uber_jar">Procedure for builing Uber jar</a>
-<ul class="sectlevel3">
+<li><a href="#_procedure_for_building_an_uber_jar">Procedure for building an uber jar</a>
+<ul class="sectlevel2">
 <li><a href="#_restart_the_requestcontext_in_unit_tests">Restart the RequestContext in Unit Tests</a></li>
 <li><a href="#_attach_a_requestcontext_to_a_new_thread_in_ee">Attach a RequestContext to a New Thread in EE</a></li>
 </ul>
 </li>
 <li><a href="#_embedded_servlet_support">Embedded Servlet Support</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_jetty">Jetty</a></li>
 <li><a href="#_undertow">Undertow</a></li>
 <li><a href="#_tomcat">Tomcat</a></li>
 </ul>
 </li>
 </ul>
-</li>
-</ul>
                     </div>
                 
             </div>

Modified: deltaspike/site/trunk/content/documentation/data.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/data.html?rev=1679029&r1=1679028&r2=1679029&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/data.html (original)
+++ deltaspike/site/trunk/content/documentation/data.html Tue May 12 18:37:06 2015
@@ -328,7 +328,7 @@ chapters.</p>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>. For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure DeltaSpike in Maven-independent Projects</a>.</p>
@@ -422,12 +422,6 @@ configure the <code>TransactionStrategy<
 <span class="tag">&lt;/beans&gt;</span></code></pre>
 </div>
 </div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
-<div class="sectionbody">
 <div class="admonitionblock important">
 <table>
 <tr>
@@ -441,10 +435,14 @@ annotation-based entities.
 </tr>
 </table>
 </div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_core_concepts">Core Concepts</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_core_concepts">Core Concepts</h3>
-<div class="sect3">
-<h4 id="_repositories">Repositories</h4>
+<h3 id="_repositories">Repositories</h3>
 <div class="paragraph">
 <p>With the DeltaSpike Data module, it is possible to make a repository out
 of basically any abstract class or interface (using a concrete class
@@ -474,8 +472,8 @@ classes or interfaces this is the only w
 entity the repository relates to. In order to simplify this, DeltaSpike
 Data provides several base types.</p>
 </div>
-<div class="sect4">
-<h5 id="_the_code_entityrepository_code_interface">The <code>EntityRepository</code> Interface</h5>
+<div class="sect3">
+<h4 id="_the_code_entityrepository_code_interface">The <code>EntityRepository</code> Interface</h4>
 <div class="paragraph">
 <p>Although mainly intended to hold complex query logic, working with both
 a repository and an <code>EntityManager</code> in the service layer might
@@ -549,7 +547,6 @@ is introduced, as we see in the next cha
 </tr>
 </table>
 </div>
-</div>
 <div class="sect4">
 <h5 id="_the_code_abstractentityrepository_code_class">The <code>AbstractEntityRepository</code> Class</h5>
 <div class="paragraph">
@@ -574,8 +571,9 @@ be implemented in the repository.</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_deactivating_repositories">Deactivating Repositories</h4>
+</div>
+<div class="sect2">
+<h3 id="_deactivating_repositories">Deactivating Repositories</h3>
 <div class="paragraph">
 <p>Repositories can be deactivated creating a <a href="spi.html#_classdeactivator">ClassDeactivator</a>.</p>
 </div>
@@ -599,8 +597,8 @@ be implemented in the repository.</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_using_multiple_code_entitymanager_code">Using Multiple <code>EntityManager</code></h4>
+<div class="sect2">
+<h3 id="_using_multiple_code_entitymanager_code">Using Multiple <code>EntityManager</code></h3>
 <div class="paragraph">
 <p>While most applications will run just fine with a single
 <code>EntityManager</code>, there might be setups where multiple data sources are
@@ -635,8 +633,8 @@ the <code>@EntityManagerConfig</code> an
 interface.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_other_code_entitymanager_code_methods">Other <code>EntityManager</code> Methods</h4>
+<div class="sect2">
+<h3 id="_other_code_entitymanager_code_methods">Other <code>EntityManager</code> Methods</h3>
 <div class="paragraph">
 <p>While the <code>EntityRepository</code> methods should cover most interactions
 normally done with an <code>EntityManager</code>, for some specific cases it might
@@ -656,16 +654,18 @@ a JPA 2.0 <code>EntityManager</code>:</p
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_query_method_expressions">Query Method Expressions</h3>
+</div>
+<div class="sect1">
+<h2 id="_query_method_expressions">Query Method Expressions</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Good naming is a difficult aspects in software engineering. A good
 method name usually makes comments unnecessary and states exactly what
 the method does. And with method expressions, the method name is
 actually the implementation!</p>
 </div>
-<div class="sect3">
-<h4 id="_using_method_expressions">Using Method Expressions</h4>
+<div class="sect2">
+<h3 id="_using_method_expressions">Using Method Expressions</h3>
 <div class="paragraph">
 <p>Let&#8217;s start by looking at a (simplified for readability) example:</p>
 </div>
@@ -809,8 +809,8 @@ expressions:</p>
 you will notice early in case you have a typo in those expressions.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_query_ordering">Query Ordering</h4>
+<div class="sect2">
+<h3 id="_query_ordering">Query Ordering</h3>
 <div class="paragraph">
 <p>Beside comparators it is also possible to sort queries by using the
 <code>OrderBy</code> keyword, followed by the attribute name and the direction
@@ -828,8 +828,8 @@ you will notice early in case you have a
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_nested_properties">Nested Properties</h4>
+<div class="sect2">
+<h3 id="_nested_properties">Nested Properties</h3>
 <div class="paragraph">
 <p>To create a comparison on a nested property, the traversal parts can be
 separated by a <code>_</code>:</p>
@@ -846,8 +846,8 @@ separated by a <code>_</code>:</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_query_options">Query Options</h4>
+<div class="sect2">
+<h3 id="_query_options">Query Options</h3>
 <div class="paragraph">
 <p>DeltaSpike supports query options on method expressions. If you want to
 page a query, you can change the first result as well as the maximum
@@ -865,8 +865,8 @@ number of results returned:</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_method_prefix">Method Prefix</h4>
+<div class="sect2">
+<h3 id="_method_prefix">Method Prefix</h3>
 <div class="paragraph">
 <p>In case the <code>findBy</code> prefix does not comply with your team conventions,
 this can be adapted:</p>
@@ -884,8 +884,10 @@ this can be adapted:</p>
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_query_annotations">Query Annotations</h3>
+</div>
+<div class="sect1">
+<h2 id="_query_annotations">Query Annotations</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>While method expressions are fine for simple queries, they will often
 reach their limit once things get slightly more complex. Another aspect
@@ -894,8 +896,8 @@ best performance is over named queries.
 cases, the DeltaSpike Data module supports also annotating methods for
 more control on the generated query.</p>
 </div>
-<div class="sect3">
-<h4 id="_using_query_annotations">Using Query Annotations</h4>
+<div class="sect2">
+<h3 id="_using_query_annotations">Using Query Annotations</h3>
 <div class="paragraph">
 <p>The simples way to define a specific query is by annotating a method and
 providing the JPQL query string which has to be executed. In code, this
@@ -1007,8 +1009,8 @@ not JPQL but plain SQL:</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_annotation_options">Annotation Options</h4>
+<div class="sect2">
+<h3 id="_annotation_options">Annotation Options</h3>
 <div class="paragraph">
 <p>Beside providing a query string or reference, the <code>@Query</code> annotation
 provides also two more attributes:</p>
@@ -1051,8 +1053,8 @@ provides also two more attributes:</p>
 <p>Note that these options can also be applied to method expressions.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_query_options_2">Query Options</h4>
+<div class="sect2">
+<h3 id="_query_options_2">Query Options</h3>
 <div class="paragraph">
 <p>All the query options you have seen so far are more or less static. But
 sometimes you might want to apply certain query options dynamically. For
@@ -1105,8 +1107,8 @@ supported for Hibernate, EclipseLink and
 expressions.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_pagination">Pagination</h4>
+<div class="sect2">
+<h3 id="_pagination">Pagination</h3>
 <div class="paragraph">
 <p>We introduced the <code>QueryResult</code> type in the last chapter, which can also
 be used for pagination:</p>
@@ -1127,8 +1129,8 @@ QueryResult&lt;Person&gt; paged = person
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_bulk_operations">Bulk Operations</h4>
+<div class="sect2">
+<h3 id="_bulk_operations">Bulk Operations</h3>
 <div class="paragraph">
 <p>While reading entities and updating them one by one might be fine for
 many use cases, applying bulk updates or deletes is also a common usage
@@ -1153,8 +1155,8 @@ marking annotation <code>@Modifying</cod
 the number of entities affected by the bulk operation.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_optional_query_results">Optional Query Results</h4>
+<div class="sect2">
+<h3 id="_optional_query_results">Optional Query Results</h3>
 <div class="paragraph">
 <p>The JPA spec requires to throw exceptions in case the
 <code>getSingleResult()</code> method does either return no or more than one
@@ -1168,8 +1170,8 @@ sense for the current usecase. While the
 aligned with JPA, it is also possible to request optional query results.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_zero_or_one_result">Zero or One Result</h4>
+<div class="sect2">
+<h3 id="_zero_or_one_result">Zero or One Result</h3>
 <div class="paragraph">
 <p>With this option, the query returns <code>null</code> instead of throwing a
 <code>NoResultException</code> when there is no result returned. It is usable with
@@ -1199,8 +1201,8 @@ with the <code>SingleResultType.OPTIONAL
 <code>NonUniqueResultException</code> is still thrown.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_any_result">Any Result</h4>
+<div class="sect2">
+<h3 id="_any_result">Any Result</h3>
 <div class="paragraph">
 <p>If the caller does not really mind what kind if result is returned, it is
 also possible to request any result from the query. If there is no
@@ -1232,8 +1234,10 @@ annotations, the <code>singleResult</cod
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_transactions">Transactions</h3>
+</div>
+<div class="sect1">
+<h2 id="_transactions">Transactions</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>If you call any method expression, <code>@Query</code>-annotated method or a method
 from the <code>EntityRepository</code>, the repository will figure out if a
@@ -1297,10 +1301,12 @@ their queries in the <code>transactional
 implementation can be, for example, in an anonymous class).</p>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_extensions">Extensions</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_extensions">Extensions</h3>
-<div class="sect3">
-<h4 id="_query_delegates">Query Delegates</h4>
+<h3 id="_query_delegates">Query Delegates</h3>
 <div class="paragraph">
 <p>While repositories defines several base interfaces, there might still be
 the odd convenience method that is missing. This is actually intentional
@@ -1328,8 +1334,8 @@ repositories:</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_implementing_the_query_delegate">Implementing the Query Delegate</h4>
+<div class="sect2">
+<h3 id="_implementing_the_query_delegate">Implementing the Query Delegate</h3>
 <div class="paragraph">
 <p>The first step is to define an interface which contains the extra
 methods for your repositories (as shown above):</p>
@@ -1377,8 +1383,10 @@ selected.</p>
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_mapping">Mapping</h3>
+</div>
+<div class="sect1">
+<h2 id="_mapping">Mapping</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>While repositories are primarily intended to work with Entities, it
 might be preferable in some cases to have an additional mapping layer on
@@ -1474,8 +1482,8 @@ is mandatory. Also it is up to the mappe
 correctly (in this example, a conversion from a <code>PersonDto</code> parameter to
 <code>Person</code> entity and from <code>PersonId</code> to <code>Long</code> is necessary).</p>
 </div>
-<div class="sect3">
-<h4 id="_simple_mappings">Simple Mappings</h4>
+<div class="sect2">
+<h3 id="_simple_mappings">Simple Mappings</h3>
 <div class="paragraph">
 <p>In many cases it is just required to map a DTO object back and forth. For
 this case, the <code>SimpleQueryInOutMapperBase</code> class can be subclassed,
@@ -1518,8 +1526,10 @@ entity).</p>
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_jpa_criteria_api_support">JPA Criteria API Support</h3>
+</div>
+<div class="sect1">
+<h2 id="_jpa_criteria_api_support">JPA Criteria API Support</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Beside automatic query generation, the DeltaSpike Data module also
 provides a DSL-like API to create JPA 2 Criteria queries. It takes
@@ -1548,8 +1558,8 @@ strongest point is certainly its type sa
 of readability. We&#8217;re trying to provide a middle way here. A less
 powerful API, but still type safe and readable.</p>
 </div>
-<div class="sect3">
-<h4 id="_api_usage">API Usage</h4>
+<div class="sect2">
+<h3 id="_api_usage">API Usage</h3>
 <div class="paragraph">
 <p>The API is centered around the Criteria class and is targeted to provide
 a fluent interface to write criteria queries:</p>
@@ -1681,8 +1691,8 @@ method is called. This creates a JPA Typ
 repository entity. If required, further processing can be applied here.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_joins">Joins</h4>
+<div class="sect2">
+<h3 id="_joins">Joins</h3>
 <div class="paragraph">
 <p>For simple cases, restricting on the repository entity only works out
 fine, but once the Data model gets more complicated, the query will have
@@ -1731,8 +1741,8 @@ are slighly simpler as seen in the next
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_boolean_operators">Boolean Operators</h4>
+<div class="sect2">
+<h3 id="_boolean_operators">Boolean Operators</h3>
 <div class="paragraph">
 <p>By default, all query operators are concatenated as an and conjunction
 to the query. The DeltaSpike criteria API also allows to add groups of
@@ -1761,8 +1771,8 @@ disjunctions.</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_selections">Selections</h4>
+<div class="sect2">
+<h3 id="_selections">Selections</h3>
 <div class="paragraph">
 <p>It might not always be appropriate to retrieve full entities - you might
 also be interested in scalar values or by modified entity attributes.
@@ -1872,8 +1882,10 @@ selection clause:</p>
 </table>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_auditing">Auditing</h3>
+</div>
+<div class="sect1">
+<h2 id="_auditing">Auditing</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>A common requirement for entities is tracking what is being done with
 them. DeltaSpike provides a convenient way to support this requirement.</p>
@@ -1891,8 +1903,8 @@ requirement for your audits, have a look
 </tr>
 </table>
 </div>
-<div class="sect3">
-<h4 id="_activating_auditing">Activating Auditing</h4>
+<div class="sect2">
+<h3 id="_activating_auditing">Activating Auditing</h3>
 <div class="paragraph">
 <p>DeltaSpike uses an entity listener to update auditing data before
 entities get created or update. The entity listener must be activated
@@ -1938,14 +1950,14 @@ module. Alternatively, also the per enti
 XML.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_using_auditing_annotations">Using Auditing Annotations</h4>
+<div class="sect2">
+<h3 id="_using_auditing_annotations">Using Auditing Annotations</h3>
 <div class="paragraph">
 <p>All that has to be done now is annotating the entity properties which
 are used to audit the entity.</p>
 </div>
-<div class="sect4">
-<h5 id="_updating_timestamps">Updating Timestamps</h5>
+<div class="sect3">
+<h4 id="_updating_timestamps">Updating Timestamps</h4>
 <div class="paragraph">
 <p>To keep track on creation and modification times, following annotations
 can be used:</p>
@@ -1981,8 +1993,8 @@ the annotation can be customized:</p>
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_who_s_changing_my_entities">Who&#8217;s Changing My Entities?</h5>
+<div class="sect3">
+<h4 id="_who_s_changing_my_entities">Who&#8217;s Changing My Entities?</h4>
 <div class="paragraph">
 <p>Beside keeping track of when a change has happened, it is also often
 critical to track who&#8217;s responsible for the change. Annotate a user
@@ -2049,7 +2061,6 @@ provider when persisting / updating the
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -2079,30 +2090,31 @@ provider when persisting / updating the
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_1_declare_data_module_dependencies">1. Declare Data Module Dependencies</a></li>
 <li><a href="#_2_complete_additional_java_environment_configuration">2. Complete Additional Java Environment Configuration</a></li>
 <li><a href="#_3_complete_additional_project_configuration">3. Complete Additional Project Configuration</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#_core_concepts">Core Concepts</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_repositories">Repositories</a>
+<ul class="sectlevel3">
+<li><a href="#_the_code_entityrepository_code_interface">The <code>EntityRepository</code> Interface</a>
 <ul class="sectlevel4">
-<li><a href="#_the_code_entityrepository_code_interface">The <code>EntityRepository</code> Interface</a></li>
 <li><a href="#_the_code_abstractentityrepository_code_class">The <code>AbstractEntityRepository</code> Class</a></li>
 </ul>
 </li>
+</ul>
+</li>
 <li><a href="#_deactivating_repositories">Deactivating Repositories</a></li>
 <li><a href="#_using_multiple_code_entitymanager_code">Using Multiple <code>EntityManager</code></a></li>
 <li><a href="#_other_code_entitymanager_code_methods">Other <code>EntityManager</code> Methods</a></li>
 </ul>
 </li>
 <li><a href="#_query_method_expressions">Query Method Expressions</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_using_method_expressions">Using Method Expressions</a></li>
 <li><a href="#_query_ordering">Query Ordering</a></li>
 <li><a href="#_nested_properties">Nested Properties</a></li>
@@ -2111,7 +2123,7 @@ provider when persisting / updating the
 </ul>
 </li>
 <li><a href="#_query_annotations">Query Annotations</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_using_query_annotations">Using Query Annotations</a></li>
 <li><a href="#_annotation_options">Annotation Options</a></li>
 <li><a href="#_query_options_2">Query Options</a></li>
@@ -2124,18 +2136,18 @@ provider when persisting / updating the
 </li>
 <li><a href="#_transactions">Transactions</a></li>
 <li><a href="#_extensions">Extensions</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_query_delegates">Query Delegates</a></li>
 <li><a href="#_implementing_the_query_delegate">Implementing the Query Delegate</a></li>
 </ul>
 </li>
 <li><a href="#_mapping">Mapping</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_simple_mappings">Simple Mappings</a></li>
 </ul>
 </li>
 <li><a href="#_jpa_criteria_api_support">JPA Criteria API Support</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_api_usage">API Usage</a></li>
 <li><a href="#_joins">Joins</a></li>
 <li><a href="#_boolean_operators">Boolean Operators</a></li>
@@ -2143,17 +2155,15 @@ provider when persisting / updating the
 </ul>
 </li>
 <li><a href="#_auditing">Auditing</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_activating_auditing">Activating Auditing</a></li>
 <li><a href="#_using_auditing_annotations">Using Auditing Annotations</a>
-<ul class="sectlevel4">
+<ul class="sectlevel3">
 <li><a href="#_updating_timestamps">Updating Timestamps</a></li>
 <li><a href="#_who_s_changing_my_entities">Who&#8217;s Changing My Entities?</a></li>
 </ul>
 </li>
 </ul>
-</li>
-</ul>
 </li>
 </ul>
                     </div>

Modified: deltaspike/site/trunk/content/documentation/jpa.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/jpa.html?rev=1679029&r1=1679028&r2=1679029&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/jpa.html (original)
+++ deltaspike/site/trunk/content/documentation/jpa.html Tue May 12 18:37:06 2015
@@ -281,7 +281,7 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>. For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure DeltaSpike in Maven-independent Projects</a>.</p>
@@ -328,10 +328,8 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
+<h2 id="__transactional">@Transactional</h2>
 <div class="sectionbody">
-<div class="sect2">
-<h3 id="__transactional">@Transactional</h3>
 <div class="paragraph">
 <p>This annotation is an alternative to transactional EJBs which allows to
 execute a method within a transaction. Before it is possible to start
@@ -630,8 +628,10 @@ a different <code>EntityManager</code>.
 immediate rollback.</p>
 </div>
 </div>
-<div class="sect2">
-<h3 id="__transactionscoped">@TransactionScoped</h3>
+</div>
+<div class="sect1">
+<h2 id="__transactionscoped">@TransactionScoped</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p><code>@Transactional</code> also starts a context which is available as long as the
 transaction started by <code>@Transactional</code>. Besides other beans you can use
@@ -670,8 +670,10 @@ this scope for the <code>EntityManager</
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_extended_persistence_contexts">Extended Persistence Contexts</h3>
+</div>
+<div class="sect1">
+<h2 id="_extended_persistence_contexts">Extended Persistence Contexts</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Frameworks like MyFaces Orchestra provide a feature which allows keeping
 an <code>EntityManager</code> across multiple requests. That means it is not
@@ -794,8 +796,10 @@ serialized as well. However, as mentione
 such an approach.</p>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_jta_support">JTA Support</h3>
+</div>
+<div class="sect1">
+<h2 id="_jta_support">JTA Support</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>By default the transaction-type used by <code>@Transactional</code> is
 <code>RESOURCE_LOCAL</code>. If you configure <code>transaction-type="JTA"</code> in the
@@ -838,7 +842,6 @@ to <code>/META-INF/apache-deltaspike.pro
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -869,21 +872,17 @@ to <code>/META-INF/apache-deltaspike.pro
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_1_declare_jpa_module_dependencies">1. Declare JPA Module Dependencies</a></li>
 <li><a href="#_2_enable_the_transaction_interceptor">2. Enable the Transaction Interceptor</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#__transactional">@Transactional</a></li>
 <li><a href="#__transactionscoped">@TransactionScoped</a></li>
 <li><a href="#_extended_persistence_contexts">Extended Persistence Contexts</a></li>
 <li><a href="#_jta_support">JTA Support</a></li>
 </ul>
-</li>
-</ul>
                     </div>
                 
             </div>

Modified: deltaspike/site/trunk/content/documentation/jsf.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/jsf.html?rev=1679029&r1=1679028&r2=1679029&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/jsf.html (original)
+++ deltaspike/site/trunk/content/documentation/jsf.html Tue May 12 18:37:06 2015
@@ -281,7 +281,7 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>. For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure DeltaSpike in Maven-independent Projects</a>.</p>
@@ -321,12 +321,6 @@ table.CodeRay td.code>pre{padding:0}
 <span class="tag">&lt;/dependency&gt;</span></code></pre>
 </div>
 </div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
-<div class="sectionbody">
 <div class="admonitionblock important">
 <table>
 <tr>
@@ -343,8 +337,12 @@ the corresponding impact.
 </tr>
 </table>
 </div>
-<div class="sect2">
-<h3 id="_jsf_messages">JSF Messages</h3>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_jsf_messages">JSF Messages</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>DeltaSpike provides an injectable component for typesafe FacesMessages.</p>
 </div>
@@ -382,12 +380,14 @@ In case of a String we use it for both t
 <p>If a Message is returned, we lookup the 'detail' and 'summary' categories (see <code>org.apache.deltaspike.core.api.message.Message#toString(String)</code> for creating the FacesMessage.</p>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_multi_window_handling">Multi-Window Handling</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_multi_window_handling">Multi-Window Handling</h3>
+<h3 id="_background">Background</h3>
 <div class="sect3">
-<h4 id="_background">Background</h4>
-<div class="sect4">
-<h5 id="_historic_considerations">Historic Considerations</h5>
+<h4 id="_historic_considerations">Historic Considerations</h4>
 <div class="paragraph">
 <p>Until the end of the 1990s web browsers are usually single threaded and
 only had one window. But in the last years browsers supporting multiple
@@ -398,8 +398,8 @@ maintaining web application data in @Ses
 still used in most of the cases.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_how_jsf_2_changed_the_world">How JSF-2 Changed the World</h5>
+<div class="sect3">
+<h4 id="_how_jsf_2_changed_the_world">How JSF-2 Changed the World</h4>
 <div class="paragraph">
 <p>The MyFaces Orchestra community did a good summary about the various
 ways to handle multiple window support in JSF Applications. Those
@@ -411,8 +411,8 @@ links, a typical JSF-2 application conta
 used to see in JSF-1, thus we have far more href links to cope with.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_standard_windowid_handling">Standard windowId Handling</h5>
+<div class="sect3">
+<h4 id="_standard_windowid_handling">Standard windowId Handling</h4>
 <div class="paragraph">
 <p>With a classical approach we would not be able to simply add a windowId
 parameter to such links because if the user would open the link in a new
@@ -430,10 +430,10 @@ not feasible as general solution.</p>
 </div>
 </div>
 </div>
+<div class="sect2">
+<h3 id="_available_modes">Available Modes</h3>
 <div class="sect3">
-<h4 id="_available_modes">Available Modes</h4>
-<div class="sect4">
-<h5 id="_clientwindow">CLIENTWINDOW</h5>
+<h4 id="_clientwindow">CLIENTWINDOW</h4>
 <div class="paragraph">
 <p>Each GET request results in an intermediate small html page which checks
 if the browser tab fits the requested windowId. When the windowId is
@@ -443,8 +443,8 @@ dsRid/windowId will be added. On the ser
 will be extracted from the cookie. For POST request detection, the
 windowId will be added as hidden input to all forms.</p>
 </div>
-<div class="sect5">
-<h6 id="_advantage">Advantage</h6>
+<div class="sect4">
+<h5 id="_advantage">Advantage</h5>
 <div class="ulist">
 <ul>
 <li>
@@ -453,8 +453,8 @@ windowId will be added as hidden input t
 </ul>
 </div>
 </div>
-<div class="sect5">
-<h6 id="_disadvantage">Disadvantage</h6>
+<div class="sect4">
+<h5 id="_disadvantage">Disadvantage</h5>
 <div class="ulist">
 <ul>
 <li>
@@ -476,8 +476,8 @@ directly.</p>
 </ul>
 </div>
 </div>
-<div class="sect5">
-<h6 id="_change_windowhandler_html">Change windowhandler.html</h6>
+<div class="sect4">
+<h5 id="_change_windowhandler_html">Change windowhandler.html</h5>
 <div class="paragraph">
 <p>To customize the look and feel of the windowhandler.html, you can simply
 provide a own via:</p>
@@ -497,8 +497,8 @@ provide a own via:</p>
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_lazy">LAZY</h5>
+<div class="sect3">
+<h4 id="_lazy">LAZY</h4>
 <div class="paragraph">
 <p>Always appends the windowId to all, from JSF generated, URLs. On the
 first GET request without a windowId, it will generate a new windowId
@@ -509,8 +509,8 @@ check if the windowId in the URL is matc
 it is not matching, the view will be refreshed with the right windowId in
 the URL.</p>
 </div>
-<div class="sect5">
-<h6 id="_advantage_2">Advantage</h6>
+<div class="sect4">
+<h5 id="_advantage_2">Advantage</h5>
 <div class="ulist">
 <ul>
 <li>
@@ -519,8 +519,8 @@ the URL.</p>
 </ul>
 </div>
 </div>
-<div class="sect5">
-<h6 id="_disadvantage_2">Disadvantage</h6>
+<div class="sect4">
+<h5 id="_disadvantage_2">Disadvantage</h5>
 <div class="ulist">
 <ul>
 <li>
@@ -532,8 +532,8 @@ the windowId matches the <code>window.na
 </ul>
 </div>
 </div>
-<div class="sect5">
-<h6 id="_workflow_example">Workflow Example</h6>
+<div class="sect4">
+<h5 id="_workflow_example">Workflow Example</h5>
 <div class="paragraph">
 <p>First GET request with windowId</p>
 </div>
@@ -599,8 +599,8 @@ from <code>window.name</code></p>
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_none">NONE</h5>
+<div class="sect3">
+<h4 id="_none">NONE</h4>
 <div class="paragraph">
 <p>Any window or browser tab detection will be disabled for the current
 request. Scopes like @WindowScoped, @GroupedConversationScoped or
@@ -609,15 +609,15 @@ current request does not support Javascr
 bot/crawler.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_delegated">DELEGATED</h5>
+<div class="sect3">
+<h4 id="_delegated">DELEGATED</h4>
 <div class="paragraph">
 <p>Delegates the complete window handling to the new JSF 2.2 ClientWindow
 (if not disabled).</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_custom">CUSTOM</h5>
+<div class="sect3">
+<h4 id="_custom">CUSTOM</h4>
 <div class="paragraph">
 <p>Enables to use an complete own
 <code>org.apache.deltaspike.jsf.spi.scope.window.ClientWindow</code>
@@ -625,10 +625,10 @@ implementation.</p>
 </div>
 </div>
 </div>
+<div class="sect2">
+<h3 id="_configuration">Configuration</h3>
 <div class="sect3">
-<h4 id="_configuration">Configuration</h4>
-<div class="sect4">
-<h5 id="_ds_windowid">ds:windowId</h5>
+<h4 id="_ds_windowid">ds:windowId</h4>
 <div class="paragraph">
 <p>The component <code>ds:windowId</code>
 (<code>xmlns:ds="http://deltaspike.apache.org/jsf"</code>) is required to enable
@@ -638,8 +638,8 @@ mode. The best way, to apply it for all
 to all of your templates.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_ds_disableclientwindow">ds:disableClientWindow</h5>
+<div class="sect3">
+<h4 id="_ds_disableclientwindow">ds:disableClientWindow</h4>
 <div class="paragraph">
 <p>Similiar to JSF 2.2' <code>disableClientWindow</code> attribute,
 <code>ds:disableClientWindow</code> provides the ability to disable the rendering
@@ -654,8 +654,8 @@ of the windowId to all links of all chil
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_number_of_active_windows">Number of Active Windows</h5>
+<div class="sect3">
+<h4 id="_number_of_active_windows">Number of Active Windows</h4>
 <div class="paragraph">
 <p>By default, DeltaSpike allows <code>1024</code> active windows per session. Anyway, this number is reduced inside this JSF module to <code>64</code> for JSF applications. Once that the limit number of active windows is reached, DeltaSpike will drop the oldest active window.</p>
 </div>
@@ -680,8 +680,8 @@ of the windowId to all links of all chil
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_switch_mode">Switch Mode</h5>
+<div class="sect3">
+<h4 id="_switch_mode">Switch Mode</h4>
 <div class="paragraph">
 <p>To switch the mode, just provide a
 <code>org.apache.deltaspike.jsf.api.config.JsfModuleConfig</code> and overwrite
@@ -701,8 +701,8 @@ of the windowId to all links of all chil
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_provide_a_custom_clientwindow">Provide a Custom ClientWindow</h5>
+<div class="sect3">
+<h4 id="_provide_a_custom_clientwindow">Provide a Custom ClientWindow</h4>
 <div class="paragraph">
 <p>If you would like to provide an custom
 <code>org.apache.deltaspike.jsf.spi.scope.window.ClientWindow</code>
@@ -736,8 +736,8 @@ implementation, you can just do it, for
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_based_scopes">Based Scopes</h4>
+<div class="sect2">
+<h3 id="_based_scopes">Based Scopes</h3>
 <div class="ulist">
 <ul>
 <li>
@@ -753,10 +753,12 @@ implementation, you can just do it, for
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_scopes">Scopes</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_scopes">Scopes</h3>
-<div class="sect3">
-<h4 id="__windowscoped">@WindowScoped</h4>
+<h3 id="__windowscoped">@WindowScoped</h3>
 <div class="paragraph">
 <p>The window-scope is like a session per window. That means that the data
 is bound to a window/tab and it not shared between windows (like the
@@ -774,8 +776,8 @@ between windows.</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="__viewaccessscoped">@ViewAccessScoped</h4>
+<div class="sect2">
+<h3 id="__viewaccessscoped">@ViewAccessScoped</h3>
 <div class="paragraph">
 <p>In case of conversations you have to un-scope beans manually (or they
 will be terminated automatically after a timeout). However, sometimes
@@ -815,22 +817,22 @@ tab' on a page with a @ViewAccessScoped
 </table>
 </div>
 </div>
-<div class="sect3">
-<h4 id="__groupedconversationscoped_from_deltaspike_0_6">@GroupedConversationScoped (From DeltaSpike 0.6)</h4>
+<div class="sect2">
+<h3 id="__groupedconversationscoped">@GroupedConversationScoped</h3>
 <div class="paragraph">
 <p>See (Grouped-)Conversations</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="__viewscoped">@ViewScoped</h4>
+<div class="sect2">
+<h3 id="__viewscoped">@ViewScoped</h3>
 <div class="paragraph">
 <p>DeltaSpike provides an CDI context for the JSF 2.0/2.1
 @javax.faces.bean.ViewScoped. You can simply annotate your bean with
 @javax.faces.bean.ViewScoped and @Named.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_jsf_2_0_scopes">JSF 2.0 Scopes</h4>
+<div class="sect2">
+<h3 id="_jsf_2_0_scopes">JSF 2.0 Scopes</h3>
 <div class="paragraph">
 <p>JSF 2.0 introduced new annotations as well as a new scope - the View
 Scope. CODI allows to use all the CDI mechanisms in beans annotated
@@ -863,8 +865,10 @@ CDI annotation.</p>
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_integration_with_deltaspike_type_safe_messages">Integration with DeltaSpike Type-safe Messages</h3>
+</div>
+<div class="sect1">
+<h2 id="_integration_with_deltaspike_type_safe_messages">Integration with DeltaSpike Type-safe Messages</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>You can use <a href="core.html#_messages_i18n">DeltaSpike type-safe messages</a>
 with JSF to provide i18n messages and test to an JSF appplicaton.</p>
@@ -933,10 +937,12 @@ javax.faces.component.UIInput.REQUIRED =
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_type_safe_view_configs">Type-safe View-Configs</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_type_safe_view_configs">Type-safe View-Configs</h3>
-<div class="sect3">
-<h4 id="_intro">Intro</h4>
+<h3 id="_intro">Intro</h3>
 <div class="paragraph">
 <p>Type-safe view-configs are static configs which can be used in
 combination with every view-technology which is based on Java. Currently
@@ -961,8 +967,8 @@ on the basic API provided by the Core. S
 custom concepts the same way DeltaSpike itself does.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_motivation">Motivation</h4>
+<div class="sect2">
+<h3 id="_motivation">Motivation</h3>
 <div class="paragraph">
 <p>Instead of learning the concepts and rules of view-configs provided by
 DeltaSpike, it might be easier for simple demos to just type some
@@ -1033,16 +1039,16 @@ more work <strong>initially</strong>?</p
 <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>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_bean_discovery_mode_annotated">Bean-discovery-mode Annotated</h4>
+<div class="sect2">
+<h3 id="_bean_discovery_mode_annotated">Bean-discovery-mode Annotated</h3>
 <div class="paragraph">
 <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 tip at
 @ViewConfigRoot</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_basic_api_usages">Basic API Usages</h4>
+<div class="sect2">
+<h3 id="_basic_api_usages">Basic API Usages</h3>
 <div class="paragraph">
 <p>While reading this section keep the following simple rules in mind:
 Meta-data gets inherited along the path of Java inheritance
@@ -1181,8 +1187,8 @@ navigation target of this method is with
 }</code></pre>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_file_view_and_folder_folder_paths">File (@View) and Folder (@Folder) Paths</h5>
+<div class="sect3">
+<h4 id="_file_view_and_folder_folder_paths">File (@View) and Folder (@Folder) Paths</h4>
 <div class="paragraph">
 <p><code>@View</code> as well as <code>@Folder</code> are optional annotations. <code>@Folder</code> is only
 needed for using a different folder-name or for marking folder configs
@@ -1247,8 +1253,8 @@ Pages.Wizard1.Step1).</p>
 <code>@View#name</code> and <code>@View#extension</code> (or you register custom
 `NameBuilder`s inline or globally).</p>
 </div>
-<div class="sect5">
-<h6 id="__folder_name">@Folder#name</h6>
+<div class="sect4">
+<h5 id="__folder_name">@Folder#name</h5>
 <div class="paragraph">
 <p>The rules are pretty simple. You will get what you write. There are only
 two additional features:</p>
@@ -1304,8 +1310,8 @@ two additional features:</p>
 </ul>
 </div>
 </div>
-<div class="sect5">
-<h6 id="__view">@View</h6>
+<div class="sect4">
+<h5 id="__view">@View</h5>
 <div class="paragraph">
 <p>The same naming rules apply to <code>@View#basePath</code>. However, it is only
 valid to be used at view-config nodes which represent pages (&#8594; classes
@@ -1399,8 +1405,8 @@ inherited along the inheritance path.</p
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_navigation_parameters">Navigation Parameters</h5>
+<div class="sect3">
+<h4 id="_navigation_parameters">Navigation Parameters</h4>
 <div class="paragraph">
 <p>Since the view-config is static, an approach to add parameters is
 needed. The following part shows different possibilities to add
@@ -1413,8 +1419,8 @@ using <code>@View(navigation = REDIRECT)
 <code>"includeViewParams=true"</code> and <code>@View(viewParams = INCLUDE)</code>.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_static_configuration_via_navigationparameter">Static Configuration via @NavigationParameter</h5>
+<div class="sect3">
+<h4 id="_static_configuration_via_navigationparameter">Static Configuration via @NavigationParameter</h4>
 <div class="paragraph">
 <p>In some cases, it is needed to add an information in any case. So you can
 annotate the view-config class with <code>@NavigationParameter</code>. Supported
@@ -1461,8 +1467,8 @@ them statically for particular methods:<
 }</code></pre>
 </div>
 </div>
-<div class="sect5">
-<h6 id="_dynamic_configuration_via_navigationparametercontext">Dynamic Configuration via NavigationParameterContext</h6>
+<div class="sect4">
+<h5 id="_dynamic_configuration_via_navigationparametercontext">Dynamic Configuration via NavigationParameterContext</h5>
 <div class="paragraph">
 <p>Instead of using parameters in a static fashion (as shown above), it is
 also possible to add them dynamically (e.g. in case of special
@@ -1494,8 +1500,8 @@ conditions).</p>
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_security_integration_via_secured">Security Integration via @Secured</h5>
+<div class="sect3">
+<h4 id="_security_integration_via_secured">Security Integration via @Secured</h4>
 <div class="paragraph">
 <p>This annotation is a custom view-meta-data provided by the
 Security-module which allows to integrate third-party frameworks (or
@@ -1579,8 +1585,8 @@ this case you would need:</p>
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_view_controller_callbacks_via_viewcontrollerref">View-Controller Callbacks via @ViewControllerRef</h5>
+<div class="sect3">
+<h4 id="_view_controller_callbacks_via_viewcontrollerref">View-Controller Callbacks via @ViewControllerRef</h4>
 <div class="paragraph">
 <p>This annotation is a custom view-meta-data provided by the JSF-module
 which allows to configure beans which should act as view-controllers.
@@ -1633,8 +1639,8 @@ display the exception.</p>
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_referencing_views_via_viewref">Referencing Views via @ViewRef</h5>
+<div class="sect3">
+<h4 id="_referencing_views_via_viewref">Referencing Views via @ViewRef</h4>
 <div class="paragraph">
 <p>With <code>@ViewControllerRef#value</code> you can annotate a view-config class to
 bind (/reference) a controller to it. <code>@ViewRef#config</code> allows the same
@@ -1669,8 +1675,8 @@ many view/s.</p>
 pages).</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_using_the_optional_viewnavigationhandler">Using the (Optional) ViewNavigationHandler</h5>
+<div class="sect3">
+<h4 id="_using_the_optional_viewnavigationhandler">Using the (Optional) ViewNavigationHandler</h4>
 <div class="paragraph">
 <p>With JSF you typically navigate with the action-method bound to a
 command-component. However, also JSF supports manual navigation via
@@ -1706,8 +1712,8 @@ process, since <code>ViewNavigationHandl
 navigation-handler (of JSF).</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_configuring_a_default_error_view">Configuring a Default Error-View</h5>
+<div class="sect3">
+<h4 id="_configuring_a_default_error_view">Configuring a Default Error-View</h4>
 <div class="paragraph">
 <p>It is possible to mark one view-config class as default error-view. That
 means in case of errors it will be used as navigation target
@@ -1774,8 +1780,8 @@ in the JSF request-lifecycle for a navig
 transformed to a standard (implicit) JSF navigation.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_using_viewconfigresolver">Using ViewConfigResolver</h5>
+<div class="sect3">
+<h4 id="_using_viewconfigresolver">Using ViewConfigResolver</h4>
 <div class="paragraph">
 <p>If you would like to query view-meta-data yourself (for whatever
 reason), you can do that with <code>ViewConfigResolver</code>.</p>
@@ -1834,10 +1840,10 @@ configured (view-)meta-data and get and/
 </div>
 </div>
 </div>
+<div class="sect2">
+<h3 id="_advanced_api_usages">Advanced API Usages</h3>
 <div class="sect3">
-<h4 id="_advanced_api_usages">Advanced API Usages</h4>
-<div class="sect4">
-<h5 id="_creating_custom_meta_data_via_viewmetadata">Creating Custom Meta-Data via @ViewMetaData</h5>
+<h4 id="_creating_custom_meta_data_via_viewmetadata">Creating Custom Meta-Data via @ViewMetaData</h4>
 <div class="paragraph">
 <p>This meta-annotation allows to create custom view-meta-data which can be
 used for view-configs. By default meta-data of a lower level overrides
@@ -1867,8 +1873,8 @@ ViewConfigDescriptor viewConfigDescripto
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_creating_custom_meta_data_via_stereotype">Creating Custom Meta-Data via @Stereotype</h5>
+<div class="sect3">
+<h4 id="_creating_custom_meta_data_via_stereotype">Creating Custom Meta-Data via @Stereotype</h4>
 <div class="paragraph">
 <p>Like with CDI itself you can encapsulate multiple view meta-data
 annotation in one annotation.</p>
@@ -1898,8 +1904,8 @@ are by default transparent.</p>
 well, once you annotate them with <code>@ViewMetaData</code>.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_creating_custom_callbacks_via_viewmetadata">Creating Custom Callbacks via @ViewMetaData</h5>
+<div class="sect3">
+<h4 id="_creating_custom_callbacks_via_viewmetadata">Creating Custom Callbacks via @ViewMetaData</h4>
 <div class="paragraph">
 <p>Via a custom ConfigPreProcessor it is possible to register custom
 callbacks dynamically. The following listing shows a view-config which
@@ -1964,8 +1970,8 @@ the type of the callback (= class of the
 parameter for <code>#getExecutableCallbackDescriptor</code>.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_creating_custom_inline_meta_data_via_inlineviewmetadata">Creating Custom inline Meta-Data via @InlineViewMetaData</h5>
+<div class="sect3">
+<h4 id="_creating_custom_inline_meta_data_via_inlineviewmetadata">Creating Custom inline Meta-Data via @InlineViewMetaData</h4>
 <div class="paragraph">
 <p>This annotation can be used for view-meta-data which can be placed on
 other classes than view-config-classes. It is used, for example, for <code>@ViewRef</code>.
@@ -1978,8 +1984,8 @@ meta-data representation which is used f
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_path_validation">Path-Validation</h4>
+<div class="sect2">
+<h3 id="_path_validation">Path-Validation</h3>
 <div class="paragraph">
 <p>DeltaSpike (after v0.5) validates your configs out-of-the-box. The
 application will fail to start, if there is an invalid config (e.g. a
@@ -1994,10 +2000,10 @@ which restricts
 <code>org.apache.deltaspike.jsf.impl.config.view.ViewConfigPathValidator</code>.</p>
 </div>
 </div>
+<div class="sect2">
+<h3 id="_view_config_spi">View-Config SPI</h3>
 <div class="sect3">
-<h4 id="_view_config_spi">View-Config SPI</h4>
-<div class="sect4">
-<h5 id="_configdescriptorvalidator">ConfigDescriptorValidator</h5>
+<h4 id="_configdescriptorvalidator">ConfigDescriptorValidator</h4>
 <div class="paragraph">
 <p>Allows to validate the final view-config descriptors before they get
 deployed. Since the config-descriptor contains, for example, the final path, it is
@@ -2005,22 +2011,22 @@ also possible to validate if the corresp
 <code>@ViewConfigRoot</code> to configure 1-n validators.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_confignodeconverter">ConfigNodeConverter</h5>
+<div class="sect3">
+<h4 id="_confignodeconverter">ConfigNodeConverter</h4>
 <div class="paragraph">
 <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>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_configpreprocessor">ConfigPreProcessor</h5>
+<div class="sect3">
+<h4 id="_configpreprocessor">ConfigPreProcessor</h4>
 <div class="paragraph">
 <p>Allows to change the found meta-data (e.g. replace default values,
 callbacks,&#8230;&#8203;) or the <code>ViewConfigNode</code> itself.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_inlinemetadatatransformer">InlineMetaDataTransformer</h5>
+<div class="sect3">
+<h4 id="_inlinemetadatatransformer">InlineMetaDataTransformer</h4>
 <div class="paragraph">
 <p>Allows to transform an annotation annotated with <code>@InlineViewMetaData</code>
 to an annotation annotated with <code>@ViewMetaData</code>. This transformer is
@@ -2030,15 +2036,15 @@ the inline-meta-data needs a different s
 <code>@ViewControllerRef</code>.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_targetviewconfigprovider">TargetViewConfigProvider</h5>
+<div class="sect3">
+<h4 id="_targetviewconfigprovider">TargetViewConfigProvider</h4>
 <div class="paragraph">
 <p>Allows to provide a custom reference to <code>ViewConfig</code> classes (see for example
 <code>@InlineViewMetaData</code> and <code>@ViewRef</code>)</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_viewconfiginheritancestrategy">ViewConfigInheritanceStrategy</h5>
+<div class="sect3">
+<h4 id="_viewconfiginheritancestrategy">ViewConfigInheritanceStrategy</h4>
 <div class="paragraph">
 <p>Allows to customize the inheritance-strategy for meta-data. For example,
 inheritance via standard java inheritance vs. inheritance via nested
@@ -2046,15 +2052,15 @@ interfaces. Use <code>@ViewConfigRoot</c
 inheritance-strategy.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_viewconfignode">ViewConfigNode</h5>
+<div class="sect3">
+<h4 id="_viewconfignode">ViewConfigNode</h4>
 <div class="paragraph">
 <p>Node-type used for building the meta-data-tree during the bootstrapping
 process.</p>
 </div>
 </div>
-<div class="sect4">
-<h5 id="__viewconfigroot">@ViewConfigRoot</h5>
+<div class="sect3">
+<h4 id="__viewconfigroot">@ViewConfigRoot</h4>
 <div class="paragraph">
 <p>Optional annotation which allows to provide custom implementations. Only
 annotate one <code>ViewConfig</code> class which represents the root node.</p>
@@ -2079,8 +2085,8 @@ example:</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_activation_of_custom_naming_conventions">Activation of Custom Naming Conventions</h4>
+<div class="sect2">
+<h3 id="_activation_of_custom_naming_conventions">Activation of Custom Naming Conventions</h3>
 <div class="paragraph">
 <p>DeltaSpike allows to customize the default naming convention via
 <code>View.DefaultBasePathBuilder</code> and/or <code>View.DefaultFileNameBuilder</code>
@@ -2093,11 +2099,10 @@ is possible via <code>Folder.folderNameB
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="__grouped_conversations">(Grouped-)Conversations</h3>
-<div class="paragraph">
-<p>Available from DeltaSpike 0.6.</p>
 </div>
+<div class="sect1">
+<h2 id="__grouped_conversations">(Grouped-)Conversations</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>DeltaSpike conversations are based on the window-scope. Therefore, do not
 forget to add the <code>ds:windowId</code>
@@ -2254,8 +2259,8 @@ producer methods).</p>
 }</code></pre>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_terminating_conversations">Terminating Conversations</h4>
+<div class="sect2">
+<h3 id="_terminating_conversations">Terminating Conversations</h3>
 <div class="paragraph">
 <p>You can inject the conversation via <code>@Inject</code> and use it to terminate
 the conversation immediately or you inject the
@@ -2384,8 +2389,8 @@ you can close them in a <code>@PostRende
 </table>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_sub_conversation_groups">Sub-Conversation-Groups</h4>
+<div class="sect2">
+<h3 id="_sub_conversation_groups">Sub-Conversation-Groups</h3>
 <div class="paragraph">
 <p>Due to the parallel conversation concept of DeltaSpike there is no need
 of something like nested conversations. Just use them in parallel and
@@ -2470,10 +2475,12 @@ be closed as soon as you close the Impli
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_injection_in_jsf_artifacts">Injection in JSF Artifacts</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_injection_in_jsf_artifacts">Injection in JSF Artifacts</h3>
-<div class="sect3">
-<h4 id="_converter_and_validator">Converter and Validator</h4>
+<h3 id="_converter_and_validator">Converter and Validator</h3>
 <div class="paragraph">
 <p>Per default the JSF module of DeltaSpike handles JSF converters and validators as std. CDI beans and
 therefore it&#8217;s possible to use injection, lifecycle-callbacks, scope-annotations,&#8230;&#8203;
@@ -2481,8 +2488,8 @@ the same way as with any other CDI bean.
 The usage is the same as for <code>PhaseListener</code> s.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_phaselistener">PhaseListener</h4>
+<div class="sect2">
+<h3 id="_phaselistener">PhaseListener</h3>
 <div class="paragraph">
 <p>Once a std. JSF-<code>PhaseListener</code> is annotated with <code>@org.apache.deltaspike.jsf.api.listener.phase.JsfPhaseListener</code>,
 that <code>PhaseListener</code> gets active without additional config in <code>faces-config.xml</code>.
@@ -2523,10 +2530,12 @@ DeltaSpike itself uses it internally e.g
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_event_broadcasting">Event broadcasting</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_event_broadcasting">Event broadcasting</h3>
-<div class="sect3">
-<h4 id="_observe_faces_requests">Observe Faces-Requests</h4>
+<h3 id="_observe_faces_requests">Observe Faces-Requests</h3>
 <div class="paragraph">
 <p>It is possible to observe JSF-Requests via <code>@Observes</code> in combination with
 <code>@org.apache.deltaspike.core.api.lifecycle.Initialized</code> or
@@ -2548,8 +2557,8 @@ DeltaSpike itself uses it internally e.g
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_beforephase_afterphase">BeforePhase / AfterPhase</h4>
+<div class="sect2">
+<h3 id="_beforephase_afterphase">BeforePhase / AfterPhase</h3>
 <div class="paragraph">
 <p>It is possible to observe JSF request-lifecycle phase-events via <code>@Observes</code> in combination with
 <code>@org.apache.deltaspike.jsf.api.listener.phase.BeforePhase</code> or
@@ -2571,8 +2580,8 @@ DeltaSpike itself uses it internally e.g
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_jsf_systemevents">JSF SystemEvents</h4>
+<div class="sect2">
+<h3 id="_jsf_systemevents">JSF SystemEvents</h3>
 <div class="paragraph">
 <p>Following JSF SystemEvents can be observed via CDI:</p>
 </div>
@@ -2604,17 +2613,19 @@ DeltaSpike itself uses it internally e.g
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_intergration_with_exception_control_from_deltaspike_0_6">Intergration with Exception Control (from DeltaSpike 0.6)</h3>
+</div>
+<div class="sect1">
+<h2 id="_integration_with_exception_control">Integration with Exception Control</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Whenever a unhandled exception occurs within the JSF lifecycle, our JSF
 ExceptionHandler provides a integration to the DeltaSpike Exception
 Control.</p>
 </div>
+<div class="sect2">
+<h3 id="_examples">Examples</h3>
 <div class="sect3">
-<h4 id="_examples">Examples</h4>
-<div class="sect4">
-<h5 id="_basic">Basic</h5>
+<h4 id="_basic">Basic</h4>
 <div class="listingblock">
 <div class="content">
 <pre>@ExceptionHandler
@@ -2631,8 +2642,8 @@ public class ApplicationExceptionHandler
 </div>
 </div>
 </div>
-<div class="sect4">
-<h5 id="_redirect">Redirect</h5>
+<div class="sect3">
+<h4 id="_redirect">Redirect</h4>
 <div class="listingblock">
 <div class="content">
 <pre class="CodeRay highlight"><code data-lang="java"><span class="annotation">@ExceptionHandler</span>
@@ -2653,8 +2664,8 @@ public class ApplicationExceptionHandler
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_using_a_custom_qualifier_for_jsf_exceptions">Using a Custom Qualifier for JSF Exceptions</h4>
+<div class="sect2">
+<h3 id="_using_a_custom_qualifier_for_jsf_exceptions">Using a Custom Qualifier for JSF Exceptions</h3>
 <div class="paragraph">
 <p>In some cases, it is required to differentiate exceptions from JSF and
 normal exceptions. This is possible via a CDI qualifier:</p>
@@ -2696,8 +2707,10 @@ normal exceptions. This is possible via
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_double_submit_prevention">Double-Submit Prevention</h3>
+</div>
+<div class="sect1">
+<h2 id="_double_submit_prevention">Double-Submit Prevention</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>To avoid that the same content of a form gets submitted and therefore
 processed multiple times, it is possible to use the tag
@@ -2723,8 +2736,10 @@ within every JSF form-tag, you would lik
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_tips">Tips</h3>
+</div>
+<div class="sect1">
+<h2 id="_tips">Tips</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Using errorView, DefaultErrorView or ViewNavigationHandler will fail
 with Weld versions older than 1.1.10 due to
@@ -2732,7 +2747,6 @@ with Weld versions older than 1.1.10 due
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -2767,34 +2781,44 @@ with Weld versions older than 1.1.10 due
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_declare_jsf_module_dependencies">Declare JSF Module Dependencies</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#_jsf_messages">JSF Messages</a></li>
 <li><a href="#_multi_window_handling">Multi-Window Handling</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_background">Background</a>
-<ul class="sectlevel4">
+<ul class="sectlevel3">
 <li><a href="#_historic_considerations">Historic Considerations</a></li>
 <li><a href="#_how_jsf_2_changed_the_world">How JSF-2 Changed the World</a></li>
 <li><a href="#_standard_windowid_handling">Standard windowId Handling</a></li>
 </ul>
 </li>
 <li><a href="#_available_modes">Available Modes</a>
+<ul class="sectlevel3">
+<li><a href="#_clientwindow">CLIENTWINDOW</a>
+<ul class="sectlevel4">
+<li><a href="#_advantage">Advantage</a></li>
+<li><a href="#_disadvantage">Disadvantage</a></li>
+<li><a href="#_change_windowhandler_html">Change windowhandler.html</a></li>
+</ul>
+</li>
+<li><a href="#_lazy">LAZY</a>
 <ul class="sectlevel4">
-<li><a href="#_clientwindow">CLIENTWINDOW</a></li>
-<li><a href="#_lazy">LAZY</a></li>
+<li><a href="#_advantage_2">Advantage</a></li>
+<li><a href="#_disadvantage_2">Disadvantage</a></li>
+<li><a href="#_workflow_example">Workflow Example</a></li>
+</ul>
+</li>
 <li><a href="#_none">NONE</a></li>
 <li><a href="#_delegated">DELEGATED</a></li>
 <li><a href="#_custom">CUSTOM</a></li>
 </ul>
 </li>
 <li><a href="#_configuration">Configuration</a>
-<ul class="sectlevel4">
+<ul class="sectlevel3">
 <li><a href="#_ds_windowid">ds:windowId</a></li>
 <li><a href="#_ds_disableclientwindow">ds:disableClientWindow</a></li>
 <li><a href="#_number_of_active_windows">Number of Active Windows</a></li>
@@ -2806,25 +2830,34 @@ with Weld versions older than 1.1.10 due
 </ul>
 </li>
 <li><a href="#_scopes">Scopes</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#__windowscoped">@WindowScoped</a></li>
 <li><a href="#__viewaccessscoped">@ViewAccessScoped</a></li>
-<li><a href="#__groupedconversationscoped_from_deltaspike_0_6">@GroupedConversationScoped (From DeltaSpike 0.6)</a></li>
+<li><a href="#__groupedconversationscoped">@GroupedConversationScoped</a></li>
 <li><a href="#__viewscoped">@ViewScoped</a></li>
 <li><a href="#_jsf_2_0_scopes">JSF 2.0 Scopes</a></li>
 </ul>
 </li>
 <li><a href="#_integration_with_deltaspike_type_safe_messages">Integration with DeltaSpike Type-safe Messages</a></li>
 <li><a href="#_type_safe_view_configs">Type-safe View-Configs</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_intro">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 class="sectlevel3">
+<li><a href="#_file_view_and_folder_folder_paths">File (@View) and Folder (@Folder) Paths</a>
 <ul class="sectlevel4">
-<li><a href="#_file_view_and_folder_folder_paths">File (@View) and Folder (@Folder) Paths</a></li>
+<li><a href="#__folder_name">@Folder#name</a></li>
+<li><a href="#__view">@View</a></li>
+</ul>
+</li>
 <li><a href="#_navigation_parameters">Navigation Parameters</a></li>
-<li><a href="#_static_configuration_via_navigationparameter">Static Configuration via @NavigationParameter</a></li>
+<li><a href="#_static_configuration_via_navigationparameter">Static Configuration via @NavigationParameter</a>
+<ul class="sectlevel4">
+<li><a href="#_dynamic_configuration_via_navigationparametercontext">Dynamic Configuration via NavigationParameterContext</a></li>
+</ul>
+</li>
 <li><a href="#_security_integration_via_secured">Security Integration via @Secured</a></li>
 <li><a href="#_view_controller_callbacks_via_viewcontrollerref">View-Controller Callbacks via @ViewControllerRef</a></li>
 <li><a href="#_referencing_views_via_viewref">Referencing Views via @ViewRef</a></li>
@@ -2834,7 +2867,7 @@ with Weld versions older than 1.1.10 due
 </ul>
 </li>
 <li><a href="#_advanced_api_usages">Advanced API Usages</a>
-<ul class="sectlevel4">
+<ul class="sectlevel3">
 <li><a href="#_creating_custom_meta_data_via_viewmetadata">Creating Custom Meta-Data via @ViewMetaData</a></li>
 <li><a href="#_creating_custom_meta_data_via_stereotype">Creating Custom Meta-Data via @Stereotype</a></li>
 <li><a href="#_creating_custom_callbacks_via_viewmetadata">Creating Custom Callbacks via @ViewMetaData</a></li>
@@ -2843,7 +2876,7 @@ with Weld versions older than 1.1.10 due
 </li>
 <li><a href="#_path_validation">Path-Validation</a></li>
 <li><a href="#_view_config_spi">View-Config SPI</a>
-<ul class="sectlevel4">
+<ul class="sectlevel3">
 <li><a href="#_configdescriptorvalidator">ConfigDescriptorValidator</a></li>
 <li><a href="#_confignodeconverter">ConfigNodeConverter</a></li>
 <li><a href="#_configpreprocessor">ConfigPreProcessor</a></li>
@@ -2858,28 +2891,28 @@ with Weld versions older than 1.1.10 due
 </ul>
 </li>
 <li><a href="#__grouped_conversations">(Grouped-)Conversations</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_terminating_conversations">Terminating Conversations</a></li>
 <li><a href="#_sub_conversation_groups">Sub-Conversation-Groups</a></li>
 </ul>
 </li>
 <li><a href="#_injection_in_jsf_artifacts">Injection in JSF Artifacts</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_converter_and_validator">Converter and Validator</a></li>
 <li><a href="#_phaselistener">PhaseListener</a></li>
 </ul>
 </li>
 <li><a href="#_event_broadcasting">Event broadcasting</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_observe_faces_requests">Observe Faces-Requests</a></li>
 <li><a href="#_beforephase_afterphase">BeforePhase / AfterPhase</a></li>
 <li><a href="#_jsf_systemevents">JSF SystemEvents</a></li>
 </ul>
 </li>
-<li><a href="#_intergration_with_exception_control_from_deltaspike_0_6">Intergration with Exception Control (from DeltaSpike 0.6)</a>
-<ul class="sectlevel3">
+<li><a href="#_integration_with_exception_control">Integration with Exception Control</a>
+<ul class="sectlevel2">
 <li><a href="#_examples">Examples</a>
-<ul class="sectlevel4">
+<ul class="sectlevel3">
 <li><a href="#_basic">Basic</a></li>
 <li><a href="#_redirect">Redirect</a></li>
 </ul>
@@ -2890,8 +2923,6 @@ with Weld versions older than 1.1.10 due
 <li><a href="#_double_submit_prevention">Double-Submit Prevention</a></li>
 <li><a href="#_tips">Tips</a></li>
 </ul>
-</li>
-</ul>
                     </div>
                 
             </div>

Modified: deltaspike/site/trunk/content/documentation/partial-bean.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/partial-bean.html?rev=1679029&r1=1679028&r2=1679029&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/partial-bean.html (original)
+++ deltaspike/site/trunk/content/documentation/partial-bean.html Tue May 12 18:37:06 2015
@@ -281,7 +281,7 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>. For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure DeltaSpike in Maven-independent Projects</a>.</p>
@@ -308,12 +308,6 @@ table.CodeRay td.code>pre{padding:0}
 <span class="tag">&lt;/dependency&gt;</span></code></pre>
 </div>
 </div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
-<div class="sectionbody">
 <div class="admonitionblock important">
 <table>
 <tr>
@@ -326,8 +320,12 @@ Currently CDI Interceptors applied via @
 </tr>
 </table>
 </div>
-<div class="sect2">
-<h3 id="__partialbeanbinding">@PartialBeanBinding</h3>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="__partialbeanbinding">@PartialBeanBinding</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Partial beans allow you to implement a generic handler to replace manual
 implementations of interfaces (or abstract classes).</p>
@@ -369,7 +367,6 @@ interface (/abstract class) to generic h
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -395,17 +392,13 @@ interface (/abstract class) to generic h
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_declare_partial_bean_module_dependencies">Declare Partial-Bean Module Dependencies</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#__partialbeanbinding">@PartialBeanBinding</a></li>
 </ul>
-</li>
-</ul>
                     </div>
                 
             </div>

Modified: deltaspike/site/trunk/content/documentation/scheduler.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/scheduler.html?rev=1679029&r1=1679028&r2=1679029&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/scheduler.html (original)
+++ deltaspike/site/trunk/content/documentation/scheduler.html Tue May 12 18:37:06 2015
@@ -281,7 +281,7 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>. For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure DeltaSpike in Maven-independent Projects</a>.</p>
@@ -350,10 +350,8 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
+<h2 id="__scheduled">@Scheduled</h2>
 <div class="sectionbody">
-<div class="sect2">
-<h3 id="__scheduled">@Scheduled</h3>
 <div class="paragraph">
 <p>Just annotate your Quartz-Jobs with <code>@Scheduled</code> and they will get
 picked up and passed to the scheduler automatically (during the
@@ -424,8 +422,10 @@ schedule/install jobs dynamically.</p>
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_manual_scheduler_control">Manual Scheduler Control</h3>
+</div>
+<div class="sect1">
+<h2 id="_manual_scheduler_control">Manual Scheduler Control</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Th SPI allows to control the scheduler (or integrate any other
 compatible scheduler as an alternative to Quartz2)</p>
@@ -471,15 +471,16 @@ start a job once (without registering it
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_custom_scheduler">Custom Scheduler</h3>
+</div>
+<div class="sect1">
+<h2 id="_custom_scheduler">Custom Scheduler</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>It is possible to replace the default integration with Quartz. Any scheduler that supports cron-expressions for job-classes can be used.
 For more information, see <a href="https://deltaspike.apache.org/javadoc/1.3.0/org/apache/deltaspike/scheduler/spi/Scheduler.html">Scheduler javadoc</a>.</p>
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -512,21 +513,17 @@ For more information, see <a href="https
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_1_declare_scheduler_module_dependencies">1. Declare Scheduler Module Dependencies</a></li>
 <li><a href="#_2_declare_external_dependencies">2. Declare External Dependencies</a></li>
 <li><a href="#_3_declare_container_control_dependency">3. Declare Container Control dependency</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#__scheduled">@Scheduled</a></li>
 <li><a href="#_manual_scheduler_control">Manual Scheduler Control</a></li>
 <li><a href="#_custom_scheduler">Custom Scheduler</a></li>
 </ul>
-</li>
-</ul>
                     </div>
                 
             </div>



Mime
View raw message