svn commit: r916160 - in /websites/staging/deltaspike/trunk/content: ./ core.html

[buildbot]

Author: buildbot
Date: Mon Jul 14 09:56:27 2014
New Revision: 916160

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/core.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 14 09:56:27 2014
@@ -1 +1 @@
-1610369
+1610370

Modified: websites/staging/deltaspike/trunk/content/core.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/core.html (original)
+++ websites/staging/deltaspike/trunk/content/core.html Mon Jul 14 09:56:27 2014
@@ -121,16 +121,10 @@ Notice:    Licensed to the Apache Softwa
 </li>
 <li><a href="#injecting-resources">Injecting Resources</a></li>
 <li><a href="#exception-control">Exception Control</a><ul>
-<li><a href="#usage">Usage</a><ul>
-<li><a href="#eventing-into-the-exception-handling-framework">Eventing into 
the exception handling framework</a></li>
-</ul>
-</li>
+<li><a href="#usage">Usage</a></li>
 <li><a href="#exception-handlers">Exception handlers</a><ul>
-<li><a href="#annotations">Annotations</a><ul>
 <li><a href="#exceptionhandler">@ExceptionHandler</a></li>
 <li><a href="#handles-and-beforehandles">@Handles and @BeforeHandles</a></li>
-</ul>
-</li>
 <li><a href="#ordinal">Ordinal</a></li>
 </ul>
 </li>
@@ -558,7 +552,6 @@ most cases, you register an exception ha
 method. Alternatively, you can handle an exception programmatically, just as
 you would observe an event in CDI.</p>
 <h3 id="usage">Usage</h3>
-<h4 id="eventing-into-the-exception-handling-framework">Eventing into the 
exception handling framework</h4>
 <p>The entire exception handling process starts with an event. This helps keep
 your application minimally coupled to DeltaSpike, but also allows for further
 extension. Exception handling in DeltaSpike is all about letting you take care
@@ -615,12 +608,11 @@ called.</p>
 <p>Exception handlers are considered equal if they both handle the same 
exception
 class, have the same qualifiers, the same ordinal and the same value for
 <code>isBeforeHandler()</code>.</p>
-<h4 id="annotations">Annotations</h4>
 <p>Exception handlers are contained within exception handler beans, which are 
CDI
 beans annotated with <code>@ExceptionHandler</code>. Exception handlers are 
methods
 which have a parameter which is an instance of <code>ExceptionEvent&lt;T 
extends
 Throwable&gt;</code> annotated with the <code>@Handles</code> annotation.</p>
-<h5 id="exceptionhandler"><code>@ExceptionHandler</code></h5>
+<h4 id="exceptionhandler"><code>@ExceptionHandler</code></h4>
 <p>The <code>@ExceptionHandler</code> annotation is simply a marker annotation 
that
 instructs the DeltaSpike exception handling CDI extension to scan the bean for
 handler methods.</p>
@@ -632,7 +624,7 @@ handler methods.</p>
 
 
 <p>That's all there is to it. Now we can begin defining exception handling 
methods on this bean.</p>
-<h5 id="handles-and-beforehandles"><code>@Handles</code> and 
<code>@BeforeHandles</code></h5>
+<h4 id="handles-and-beforehandles"><code>@Handles</code> and 
<code>@BeforeHandles</code></h4>
 <p><code>@Handles</code> is a method parameter annotation that designates a 
method as an
 exception handler. Exception handler methods are registered on beans annotated
 with <code>@ExceptionHandler</code>. DeltaSpike will discover all such methods 
at