You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org> on 2006/01/30 00:47:37 UTC
[jira] Resolved: (DIRSNICKERS-96) Fix attribute value ordering in
ModifyRequestEncoder and ModifyRequestImpl.equals()
[ http://issues.apache.org/jira/browse/DIRSNICKERS-96?page=all ]
Emmanuel Lecharny resolved DIRSNICKERS-96:
------------------------------------------
Resolution: Fixed
It has been fixed, the same day the JIRA was created.
> Fix attribute value ordering in ModifyRequestEncoder and ModifyRequestImpl.equals()
> -----------------------------------------------------------------------------------
>
> Key: DIRSNICKERS-96
> URL: http://issues.apache.org/jira/browse/DIRSNICKERS-96
> Project: Directory ASN1
> Type: Bug
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
>
> When running the ModifyRequestEncoder the ModifyRequstImpl equals() fails because the LockableAttribute.equals() is failing to match for the correct order of Attribute values in ModificationItems.
> We need to figure out what is causing this. At this point the ldap-common has the code that fails in the ModifyRequestImpl.equals() commented out. This is not good because it totally turns off attribute value checking when determining ModifyRequest equivalence.
--
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