Affects Version/s: 2.0.0-M5
Fix Version/s: 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
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.
|Field||Original Value||New Value|
|Fix Version/s||2.0.0-M7 [ 12320049 ]|
|Fix Version/s||2.0.0-M6 [ 12319540 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|5d 2h 49m||1||Emmanuel Lecharny||27/Feb/12 15:13|