Compare operation on non existing or invalid attributes causes wrong return codes

• Key: DIRSERVER-378
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Alex Karasulu
• Reporter: Stefan Zoerner

Description

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

Comments

[Stefan Zoerner]

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.

[Alex Karasulu]

Committed resolving fixes within revision 239951 here:

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

[Stefan Zoerner]

I rebuilded ApacheDS. The new Compare Handler provides the expected return codes in the situations described in this defect. Therefor I close the issue. Thanks for fixing it, Stefan