[ http://issues.apache.org/jira/browse/DIREVE-173?page=comments#action_12318526 ]
Stefan Zoerner commented on DIREVE-173: --------------------------------------- I already have a JNDI test case for the LDIF file above. Let me check the behaviour against at least two other LDAP servers, then I will file it as an attachment. > 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 > Attachments: 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
