[jira] Resolved: (DIRLDAP-36) Order of multi-valued RDN should not matters while comparing

["Alex Karasulu (JIRA)" <di...@incubator.apache.org>]

     [ http://issues.apache.org/jira/browse/DIRLDAP-36?page=all ]
     
Alex Karasulu resolved DIRLDAP-36:
----------------------------------

    Resolution: Fixed

Committed revision 232182 here:

http://svn.apache.org/viewcvs.cgi?rev=232182&view=rev


> Order of multi-valued RDN should not matters while comparing
> ------------------------------------------------------------
>
>          Key: DIRLDAP-36
>          URL: http://issues.apache.org/jira/browse/DIRLDAP-36
>      Project: Directory LDAP
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Alex Karasulu
>     Priority: Minor
>      Fix For: 0.9.2

>
> class org.apache.ldap.common.name.LdapName, method compareTo should return 0 if we compare two RDN which contains multi-valued attributes like :
> cn=test+cn=result 
> must be equals to 
> cn=result+cn=test
> This is not the case. Here is a test case (to be added to class org.apache.ldap.common.name.LdapNameTest) :
>     /**
>      * Test the equivalence of two DNs with multi-valued RDN. AttributeType are
>      * not case sensitive. Each attribute type MUST be compared. Order MUST not
>      * matters They MUST be equals.
>      *
>      * @throws  NamingException  if anything goes wrong.
>      */
>     public void testInsensitiveTypeMultiValuedAttributNotOrdered() throws NamingException
>     {
>         Name name1 = new LdapName("cn=HomeDir+cn=WorkDir");
>         Name name2 = new LdapName("cn=WorkDir+cn=HomeDir");
>         assertEquals(name1.compareTo(name2), 0);
>     }

-- 
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