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: <784549488.1125292144706.JavaMail.jira@ajax.apache.org>
Date: Mon, 29 Aug 2005 07:09:04 +0200 (CEST)
From: "Alex Karasulu (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Resolved: (DIREVE-232) Modify operation (removal) provides
 wrong return codes in two situations.
In-Reply-To: <1738876071.1125068606463.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-232?page=all ]
     
Alex Karasulu resolved DIREVE-232:
----------------------------------

    Resolution: Fixed

Committed test case and fixes in revision 264063 here:

http://svn.apache.org/viewcvs.cgi?view=rev&rev=264063

> Modify operation (removal) provides wrong return codes in two situations.
> -------------------------------------------------------------------------
>
>          Key: DIREVE-232
>          URL: http://issues.apache.org/jira/browse/DIREVE-232
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.2
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>     Priority: Minor
>      Fix For: 0.9.2
>  Attachments: ModifyRemoveTest.java
>
> The modify operation provides wrong return codes in two cases:
> 1. Removal of an attribute which does not occur in the entry (expected result is error code 16: noSuchAttribute)
> 2. Removal of an invalid attribute, i.e. not existing within the schema (expected result is error code 17: undefinedAttributeType)
> This is quite similar to DIREVE-226.
> I attach a subclass of AbstractServerTest which contains several test methods for basic removal ops. Due to the recent changes regarding schema checks, most of them succeed.  Two tests check for the return codes above (and fail). It includes also a test which deletes a required attribute (not part of RDN), which fails -- but this is expected due to the current development progress.

-- 
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