[
https://issues.apache.org/jira/browse/DIRSERVER-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1698.
------------------------------------------
Resolution: Fixed
Fixed with http://svn.apache.org/viewvc?rev=1294174&view=rev and
http://svn.apache.org/viewvc?rev=1294176&view=rev
> Search on entries with multiple AVA in RDN does not work crrectly if the
> initial RDN order is not used
> ------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1698
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1698
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M5
> Reporter: Emmanuel Lecharny
> Fix For: 2.0.0-M7
>
>
> If we create an entry using a RDN with multiple AVA, like this one :
> dn: cn=Doe+gn=John, ou=system
> ObjectClass: top
> ObjectClass: person
> cn: Doe
> gn: John
> sn: John Doe
> then searching for the entry using its DN with cn=Doe+gn=John, ou=system as a
> base, you'll get the entry. However, doing the same search but with the base
> DN gn=John+cn=Doe, ou=system, you will get nothing.
> This is due to the fact that the ParentIdAndRDN.compareTo() method use the
> String value of the RDN, so the ordering is dependent on the AVA position in
> the String.
> This is bad. We must rewrite the CcompareTo method to compare the AVA one by
> one in the correct order.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
