|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Issue Links:
|
Reference
|
|
|
|
This issue is related to:
|
|
DIRSERVER-480
Move schema checking code in LDAP protocol provider into the schema interceptor
|
|
|
|
|
|
|
| Resolution Date: |
25/Aug/05 07:14 AM
|
|
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 ...
|
|
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 ...
|
Show » |
|
Bug
Minor
Compare operation on non existing or invalid attributes causes wrong return codes
