[jira] Resolved: (DIREVE-51) Exception Handling IBS

["Alex Karasulu (JIRA)" <di...@incubator.apache.org>]

     [ http://issues.apache.org/jira/browse/DIREVE-51?page=history ]
     
Alex Karasulu resolved DIREVE-51:
---------------------------------

    Resolution: Fixed

This is coming along.  We've actually started to use it to not only trap and handle unexpected exceptions but to raise exceptions for certain circumstances.

 *..An interceptor based service used to detect, raise and handle eve exceptions
 *..in one place.  This interceptor has two modes of operation.  The first mode
 *..is as a before chain interceptor where it raises exceptions.  An example
 *..where this interceptor raises an exception is when an entry already exists
 *..at a DN and is added once again to the same DN.  The other mode is as an on
 *..error chain interceptor.  In this mode the service may wrap exceptions and
 *..add extra information to an exception which is to be thrown back at the
 *..caller.

So I guess this is a work in progress where the interceptor is created and additions need to be made.  For all practical purposes though the issue can be closed.

> Exception Handling IBS
> ----------------------
>
>          Key: DIREVE-51
>          URL: http://issues.apache.org/jira/browse/DIREVE-51
>      Project: Directory Eve
>         Type: Task
>   Components: interceptors
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu

>
> Failures will result and these need to be handled with the right kind of NamingException carrying with it unequivocal information associating it with the type of LDAP failure the exception corresponds to.  This IBS hence deals with the alignment of LDAP and JNDI error to exception mapping.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira