You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by di...@incubator.apache.org on 2004/08/28 09:35:20 UTC

[jira] Created: (DIRSNICKERS-96) Fix attribute value ordering in ModifyRequestEncoder and ModifyRequestImpl.equals()

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSNICKERS-96

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSNICKERS-96
    Summary: Fix attribute value ordering in ModifyRequestEncoder and ModifyRequestImpl.equals()
       Type: Bug

     Status: Open
   Priority: Major

    Project: Directory Snickers
 Components: 
             LDAP Provider

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Sat, 28 Aug 2004 12:34 AM
    Updated: Sat, 28 Aug 2004 12:34 AM

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


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira