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: <1933979434.1124134977680.JavaMail.jira@ajax.apache.org>
Date: Mon, 15 Aug 2005 21:42:57 +0200 (CEST)
From: "Stefan Zoerner (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIREVE-226) Compare operation on non existing or
 invalid attributes causes wrong return codes
In-Reply-To: <1626592389.1124133954336.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-226?page=all ]

Stefan Zoerner updated DIREVE-226:
----------------------------------

    Attachment: BasicCompareTests.java

Here is the test case. The tests are already included in my protocol suite and ran succesful against OpenLDAP, Sun and Active Directory. On Apache DS currently two of the three tests fail. To be more precise, the expected exceptions are not thrown.

> Compare operation on non existing or invalid attributes causes wrong return codes
> ---------------------------------------------------------------------------------
>
>          Key: DIREVE-226
>          URL: http://issues.apache.org/jira/browse/DIREVE-226
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.2
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>     Priority: Minor
>  Attachments: BasicCompareTests.java
>
> If a compare is executed on an entry, and the attribute used in this operation does not occur in  the entry, or is unknown to the schema at all, this normally leads to an error.
> Two error codes are common here:
> 16: noSuchAttribute (leads to an NoSuchAttributeException in JNDI)
> 17: undefinedAttributeType (InvalidAttributeIdentifierException)
> "Normally" means that on the servers I tested with a JNDI testcase (OpenLDAP, Sun, Active Directory), the exceptions above are thrown. On Apache DS 0.9.2 they are not. I tried to find out whether it is mandatory to raise an error here (RFC 2251, chapter 4.10), but without a clear result.
> Anyway, I will attach my testcase for your consideration on how to react on such operations ... 

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