[ http://issues.apache.org/jira/browse/DIREVE-226?page=all ]
Alex Karasulu resolved DIREVE-226:
----------------------------------
Fix Version: 0.9.2
Resolution: Fixed
Committed resolving fixes within revision 239951 here:
http://svn.apache.org/viewcvs.cgi?view=rev&rev=239951
> 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
> Fix For: 0.9.2
> 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
