[ http://issues.apache.org/jira/browse/DIREVE-173?page=comments#action_12319902 ]
Stefan Zoerner commented on DIREVE-173: --------------------------------------- I have still a case were it does not work. Unfortunately it is not possible to add the JUnit test to this issue. I guess we have to reopen it first. Anyway: Basic idea is to have an entry like this: dn: cn=Tori Amos,ou=system sn: Amos cn: Tori Amos objectclass: person objectclass: top Then change the RDN to "sn=Amos" and keep the old one. The result with current ApacheDS is an entry which looks like this: dn: sn=Amos,ou=system sn: Amos sn: Amos objectClass: person objectClass: top cn: Tori Amos Expected result is that "sn=Amos" does occur once in the entry, not twice. If someone reopens the issue, I will attach my JUnit test case on this. > On modifyRdn server now adds additional Rdn attribute > ----------------------------------------------------- > > Key: DIREVE-173 > URL: http://issues.apache.org/jira/browse/DIREVE-173 > Project: Directory Server > Type: Bug > Components: jdbm database, jndi-provider > Versions: 0.9.1 > Reporter: Alex Karasulu > Assignee: Trustin Lee > Priority: Blocker > Fix For: 0.9.2 > Attachments: ModifyRdnTest.java, modRdn.ldif > > I changed the name of an entry like ou=Users, dc=example, dc=com to ou=users, > dc=example, dc=com which had a single ou=Users. I expected this operation to > delete the old attribute rather then just add the new one. This can become a > serious issue hence the reason why its a blocker. -- 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
