Author: tandraschko
Date: Mon Jul 14 09:47:16 2014
New Revision: 1610367

URL: http://svn.apache.org/r1610367
Log:
#DELTASPIKE-642 Better structure for Core documentation

Modified:
    deltaspike/site/trunk/content/core.mdtext

Modified: deltaspike/site/trunk/content/core.mdtext
URL: 
http://svn.apache.org/viewvc/deltaspike/site/trunk/content/core.mdtext?rev=1610367&r1=1610366&r2=1610367&view=diff
==============================================================================
--- deltaspike/site/trunk/content/core.mdtext (original)
+++ deltaspike/site/trunk/content/core.mdtext Mon Jul 14 09:47:16 2014
@@ -496,10 +496,10 @@ most cases, you register an exception ha
 method. Alternatively, you can handle an exception programmatically, just as
 you would observe an event in CDI.
 
-Exception Handling - Usage
+### Exception Handling - Usage
 --------------------------
 
-### Eventing into the exception handling framework
+#### Eventing into the exception handling framework
 
 The entire exception handling process starts with an event. This helps keep
 your application minimally coupled to DeltaSpike, but also allows for further
@@ -535,7 +535,7 @@ class for use later within a try/catch b
 The event is fired with a new instance of `ExceptionToCatchEvent` constructed
 with the exception to be handled.
 
-Exception handlers
+### Exception handlers
 ------------------
 
 As an application developer (i.e., an end user of DeltaSpike's exception
@@ -568,14 +568,14 @@ Exception handlers are considered equal 
 class, have the same qualifiers, the same ordinal and the same value for
 `isBeforeHandler()`.
 
-### Exception handler annotations
+#### Exception handler annotations
 
 Exception handlers are contained within exception handler beans, which are CDI
 beans annotated with `@ExceptionHandler`. Exception handlers are methods
 which have a parameter which is an instance of `ExceptionEvent<T extends
 Throwable>` annotated with the `@Handles` annotation.
 
-#### `@ExceptionHandler`
+##### `@ExceptionHandler`
 
 The `@ExceptionHandler` annotation is simply a marker annotation that
 instructs the DeltaSpike exception handling CDI extension to scan the bean for
@@ -590,7 +590,7 @@ Let's designate a CDI bean as an excepti
 
 That's all there is to it. Now we can begin defining exception handling 
methods on this bean.
 
-#### `@Handles` and `@BeforeHandles`
+##### `@Handles` and `@BeforeHandles`
 
 `@Handles` is a method parameter annotation that designates a method as an
 exception handler. Exception handler methods are registered on beans annotated
@@ -691,7 +691,7 @@ exceptions. Should a handler throw an un
 the stack and all handling done via DeltaSpike will cease. Any exception that
 was being handled will be lost.
 
-Exception Chain Processing
+### Exception Chain Processing
 --------------------------
 
 When an exception is thrown, chances are it's nested (wrapped) inside other
@@ -738,7 +738,7 @@ If there's a handler for `PersistenceExc
 handlers for `EJBException` from being invoked, which is a good thing since
 what useful information can really be obtained from `EJBException`?
 
-Handler ordinal
+### Handler ordinal
 ---------------
 
 When DeltaSpike finds more than one handler for the same exception type, it
@@ -783,7 +783,7 @@ application developers:
 -   `ExceptionEvent`
 -   `ExceptionStackEvent`
 
-### ExceptionEvent
+#### ExceptionEvent
 
 In addition to providing information about the exception being handled, the
 `ExceptionEvent` object contains methods to control the exception handling


Reply via email to