Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <709625174.1126742036908.JavaMail.jira@ajax.apache.org>
Date: Thu, 15 Sep 2005 01:53:56 +0200 (CEST)
From: "Trustin Lee (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIREVE-164) Refactor ExceptionService and move
 integrity check code to Database.
In-Reply-To: <646396632.1118885809585.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DIREVE-164?page=comments#action_12329368 ] 

Trustin Lee commented on DIREVE-164:
------------------------------------

Let's extract integrity check code to IntegrityService or something similar just like Stefan suggested.

> Refactor ExceptionService and move integrity check code to Database.
> --------------------------------------------------------------------
>
>          Key: DIREVE-164
>          URL: http://issues.apache.org/jira/browse/DIREVE-164
>      Project: Directory Server
>         Type: Improvement
>   Components: interceptors
>     Reporter: Trustin Lee
>     Assignee: Trustin Lee
>      Fix For: 0.9.3

>
> The original duty of ExceptionService was to convert JNDI exceptions and other exceptions to LDAP exceptions, but now it is doing more than its duty; it is checking exsitance of entries, etc.
> So my idea is to move those integrity check code to Database implementation (or its abstract parent?)  We'll also need good documentation about how to implement Database.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira