[ http://issues.apache.org/jira/browse/DIRSERVER-703?page=all ]
Emmanuel Lecharny resolved DIRSERVER-703.
-----------------------------------------
Resolution: Fixed
Fixed in revision 431163 & 431164 for 1.0 and 1.1 branches.
This was a stupid mistake... (does anybody have heard about intelligent
mistakes ? ;), upName was computed before the loop which parse the others atavs.
> Creation of an entry with multivalued RDN leads to wrong DN in search results.
> ------------------------------------------------------------------------------
>
> Key: DIRSERVER-703
> URL: http://issues.apache.org/jira/browse/DIRSERVER-703
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0-RC4
> Environment: * ApacheDS 1.0 RC4 SNAPSHOT
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Assigned To: Emmanuel Lecharny
> Attachments: addedTestsToSVN.ldif, badUpnameWithRdn.patch,
> MultiValuedRdnTest.java
>
>
> I use Apache Directoty Server 1.0 RC4 SNAPSHOT with server.xml unchanged. If
> I create an entry with multivalued RDN like this:
> dn: cn=Kate Bush+sn=Bush,dc=example,dc=com
> objectclass: top
> objectclass: person
> sn: Bush
> cn: Kate Bush
> i.e.
> $ ldapmodify -D "uid=admin,ou=system" -w ****** -a -f multiValued.ldif
> adding new entry cn=Kate Bush+sn=Bush,dc=example,dc=com
> $
> the entry is returned in searches with a wrong dn:
> $ ldapsearch -D "uid=admin,ou=system" -w ****** -b "dc=example,dc=com" -s one
> "(sn=Bush)"
> version: 1
> dn: cn=Kate Bush,dc=example,dc=com
> objectclass: person
> objectclass: top
> sn: Bush
> cn: Kate Bush
> $ ldapsearch -D "uid=admin,ou=system" -w ****** -b "cn=Kate
> Bush+sn=Bush,dc=example,dc=com" -s base "(sn=Bush)"
> version: 1
> dn: cn=Kate Bush,dc=example,dc=com
> objectclass: person
> objectclass: top
> sn: Bush
> cn: Kate Bush
> $
> The expected dn is cn=Kate Bush+sn=Bush,dc=example,dc=com in both cases.
> I'll attach a JUnit test which demonstrates this issue soon.
--
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
