directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Commented: (DIRSNICKERS-96) Fix attribute value ordering in ModifyRequestEncoder and ModifyRequestImpl.equals()
Date Sat, 03 Dec 2005 14:56:31 GMT
    [ http://issues.apache.org/jira/browse/DIRSNICKERS-96?page=comments#action_12359220 ] 

Emmanuel Lecharny commented on DIRSNICKERS-96:
----------------------------------------------

Is this still a bug?  I don't think so. 

Alex could you just have look at the report and tells if it has been fixed a long time ago
but not marked as resolved?

> 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


Mime
View raw message