Author: buildbot
Date: Mon Jul 14 09:47:24 2014
New Revision: 916156
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:47:24 2014
@@ -1 +1 @@
-1610346
+1610367
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:47:24 2014
@@ -120,7 +120,7 @@ Notice: Licensed to the Apache Softwa
</ul>
</li>
<li><a href="#injecting-resources">Injecting Resources</a></li>
-<li><a href="#exception-control">Exception Control</a></li>
+<li><a href="#exception-control">Exception Control</a><ul>
<li><a href="#exception-handling-usage">Exception Handling - Usage</a><ul>
<li><a href="#eventing-into-the-exception-handling-framework">Eventing into
the exception handling framework</a></li>
</ul>
@@ -135,6 +135,8 @@ Notice: Licensed to the Apache Softwa
</li>
<li><a href="#exception-chain-processing">Exception Chain Processing</a></li>
<li><a href="#handler-ordinal">Handler ordinal</a></li>
+</ul>
+</li>
<li><a href="#apis-for-exception-information-and-flow-control">APIs for
exception information and flow control</a><ul>
<li><a href="#exceptionevent">ExceptionEvent</a></li>
</ul>
@@ -555,8 +557,9 @@ infrastructure.</p>
most cases, you register an exception handler simply by annotating a handler
method. Alternatively, you can handle an exception programmatically, just as
you would observe an event in CDI.</p>
-<h2 id="exception-handling-usage">Exception Handling - Usage</h2>
-<h3 id="eventing-into-the-exception-handling-framework">Eventing into the
exception handling framework</h3>
+<h3 id="exception-handling-usage">Exception Handling - Usage</h3>
+<hr />
+<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
@@ -588,7 +591,8 @@ an inventory database:</p>
class for use later within a try/catch block.</p>
<p>The event is fired with a new instance of
<code>ExceptionToCatchEvent</code> constructed
with the exception to be handled.</p>
-<h2 id="exception-handlers">Exception handlers</h2>
+<h3 id="exception-handlers">Exception handlers</h3>
+<hr />
<p>As an application developer (i.e., an end user of DeltaSpike's exception
handling), you'll be focused on writing exception handlers. An exception
handler is a method on a CDI bean that is invoked to handle a specific type of
@@ -613,12 +617,12 @@ 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>
-<h3 id="exception-handler-annotations">Exception handler annotations</h3>
+<h4 id="exception-handler-annotations">Exception handler 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<T
extends
Throwable></code> annotated with the <code>@Handles</code> annotation.</p>
-<h4 id="exceptionhandler"><code>@ExceptionHandler</code></h4>
+<h5 id="exceptionhandler"><code>@ExceptionHandler</code></h5>
<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>
@@ -630,7 +634,7 @@ handler methods.</p>
<p>That's all there is to it. Now we can begin defining exception handling
methods on this bean.</p>
-<h4 id="handles-and-beforehandles"><code>@Handles</code> and
<code>@BeforeHandles</code></h4>
+<h5 id="handles-and-beforehandles"><code>@Handles</code> and
<code>@BeforeHandles</code></h5>
<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
@@ -719,7 +723,8 @@ muted), unless it re-enables itself by i
exceptions. Should a handler throw an unchecked exception it will propagate up
the stack and all handling done via DeltaSpike will cease. Any exception that
was being handled will be lost.</p>
-<h2 id="exception-chain-processing">Exception Chain Processing</h2>
+<h3 id="exception-chain-processing">Exception Chain Processing</h3>
+<hr />
<p>When an exception is thrown, chances are it's nested (wrapped) inside other
exceptions. (If you've ever examined a server log, you'll appreciate this
fact). The collection of exceptions in its entirety is termed an exception
@@ -759,7 +764,8 @@ order:</p>
<p>If there's a handler for <code>PersistenceException</code>, it will likely
prevent the
handlers for <code>EJBException</code> from being invoked, which is a good
thing since
what useful information can really be obtained from
<code>EJBException</code>?</p>
-<h2 id="handler-ordinal">Handler ordinal</h2>
+<h3 id="handler-ordinal">Handler ordinal</h3>
+<hr />
<p>When DeltaSpike finds more than one handler for the same exception type, it
orders the handlers by ordinal. Handlers with higher ordinal are executed
before handlers with a lower ordinal. If DeltaSpike detects two handlers for
@@ -798,7 +804,7 @@ application developers:</p>
<li><code>ExceptionEvent</code></li>
<li><code>ExceptionStackEvent</code></li>
</ul>
-<h3 id="exceptionevent">ExceptionEvent</h3>
+<h4 id="exceptionevent">ExceptionEvent</h4>
<p>In addition to providing information about the exception being handled, the
<code>ExceptionEvent</code> object contains methods to control the exception
handling
process, such as rethrowing the exception, aborting the handler chain or
