directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Updated: (DIREVE-216) Adding new object classes to an entry removes the old ones
Date Wed, 10 Aug 2005 10:31:35 GMT
     [ http://issues.apache.org/jira/browse/DIREVE-216?page=all ]

Stefan Zoerner updated DIREVE-216:
----------------------------------

    Attachment: patch_testCase_AddOpbjectClasses.txt

I added a new method to the test cases (class org.apache.ldap.server.jndi.ModifyContextTest)
which checks my problem. With Alex changes it disappeard. But I am not sure how characteristic
the methods in ModifyContextTest really are. Do they also check the partition implementation?


The test succeeds now. But as Ugo described above the top object class still vanishes if someone
tries (I observed the same problem). Therfore, the test case is not good enough ...

> Adding new object classes to an entry removes the old ones
> ----------------------------------------------------------
>
>          Key: DIREVE-216
>          URL: http://issues.apache.org/jira/browse/DIREVE-216
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.1
>  Environment: Server: ApacheDS 0.9.1 on Windows XP 
> java version "1.5.0_03"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07)
> Client: Windows XP
> Command line tool ldapadd (from IBM Tivoli Directory Server)
> or Softerra LDAP Administrator 3.2
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>      Fix For: 0.9.2
>  Attachments: LDAPModifyAddTest.java, ldap.jar, patch_testCase_AddOpbjectClasses.txt
>
> If additional objectclasses are added to an existing entry by a client, the old ones
are lost.
>  e.g. applying the following LDIF to ApacheDS
> --8<--
> # create an entry for a person
> #
> dn: cn=Tori Amos,ou=system
> changetype: add
> objectclass: top
> objectclass: person
> cn: Tori Amos
> sn: Amos
> description: an American singer-songwriter
> # add objectclasses and uid
> #
> dn: cn=Tori Amos,ou=system
> changetype: modify
> add: objectclass
> objectclass: organizationalPerson
> objectclass: inetOrgPerson
> -
> add: uid
> uid: tamos
> -
> -->8--
> leaves an entry behind with only two (instead of all for objectclasses):
> $ ldapadd -p 10389 -D uid=admin,ou=system -w *** -f addAndModifyObjectClasses.ldif
> adding new entry cn=Tori Amos,ou=system
> modifying entry cn=Tori Amos,ou=system
> $ ldapsearch -p 10389 -b "ou=system" "(cn=Tori Amos)"
> cn=Tori Amos,ou=system
> sn=Amos
> objectclass=inetOrgPerson
> objectclass=organizationalPerson
> cn=Tori Amos
> uid=tamos
> description=an American singer-songwriter
> ---
> Expected result would be:
> cn=Tori Amos,ou=system
> sn=Amos
> objectclass=top
> objectclass=person
> objectclass=inetOrgPerson
> objectclass=organizationalPerson
> cn=Tori Amos
> uid=tamos
> description=an American singer-songwriter

-- 
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


Mime
View raw message