directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Updated: (DIREVE-173) On modifyRdn server now adds additional Rdn attribute
Date Thu, 11 Aug 2005 19:34:55 GMT
     [ ]

Stefan Zoerner updated DIREVE-173:


Here it is. Not a complete coverage of the mod rdn (still some situations left), but as least
the ops of the LDIF are included in the test methods.
I run the JNDI code successfully against OpenLDAP 2.1 and Tivoli DS 5.2. Therefor I am quite
sure that the behaviour as describeb with the tests is valid. 
In my current build of Apache DS, two of the three methods fail (those who keep the rdn).

> On modifyRdn server now adds additional Rdn attribute
> -----------------------------------------------------
>          Key: DIREVE-173
>          URL:
>      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:
For more information on JIRA, see:

View raw message