You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2004/10/31 06:15:32 UTC
[jira] Created: (DIREVE-63) create exception interceptor service
create exception interceptor service
------------------------------------
Key: DIREVE-63
URL: http://issues.apache.org/jira/browse/DIREVE-63
Project: Directory Eve
Type: Task
Components: interceptors
Reporter: Alex Karasulu
Assigned to: Alex Karasulu
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.
--
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
[jira] Reopened: (DIREVE-63) create exception interceptor service
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-63?page=history ]
Alex Karasulu reopened DIREVE-63:
---------------------------------
This should not be closed but the other issue DIREVE-65 should have been closed.
> create exception interceptor service
> ------------------------------------
>
> Key: DIREVE-63
> URL: http://issues.apache.org/jira/browse/DIREVE-63
> Project: Directory Eve
> Type: Task
> Components: interceptors
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
>
> 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.
--
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
[jira] Resolved: (DIREVE-63) create exception interceptor service
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-63?page=history ]
Alex Karasulu resolved DIREVE-63:
---------------------------------
Resolution: Fixed
Committed on revision 56124:
http://svn.apache.org/viewcvs.cgi?rev=56124&view=rev
However this is still a work in progress that will be added to as we find more to stuff in there.
> create exception interceptor service
> ------------------------------------
>
> Key: DIREVE-63
> URL: http://issues.apache.org/jira/browse/DIREVE-63
> Project: Directory Eve
> Type: Task
> Components: interceptors
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
>
> 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.
--
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