[
https://issues.apache.org/jira/browse/DIRSERVER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1394:
-----------------------------------------
Affects Version/s: (was: 1.5.5)
Fix Version/s: 1.5.5
Let's fix that at the same time than DIRSERVER-1393
> Modifying subschema subentry doesn't work in some case
> ------------------------------------------------------
>
> Key: DIRSERVER-1394
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1394
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 1.5.4
> Reporter: Stefan Seelmann
> Fix For: 1.5.5
>
>
> Adding a DESC to an existing objectClass in cn=schema fails when the
> modification sequence is add/delete:
> ------------------------------------------------------------------------
> dn: cn=schema
> changetype: modify
> add: objectClasses
> objectClasses: ( 0.9.2342.19200300.100.4.21 NAME 'pilotDSA' DESC 'This is a de
> scription' SUP dSA STRUCTURAL MAY dSAQuality X-SCHEMA 'cosine' )
> -
> delete: objectClasses
> objectClasses: ( 0.9.2342.19200300.100.4.21 NAME 'pilotDSA' SUP dSA STRUCTURAL
> MAY dSAQuality X-SCHEMA 'cosine' )
> -
> ------------------------------------------------------------------------
> The error in the server logs is:
> [16:08:04] WARN
> [org.apache.directory.server.schema.registries.DefaultObjectClassRegistry] -
> objectClass pilotDSA w/ OID 0.9.2342.19200300.100.4.21 has already been
> registered!
> I think this operation should be considered as atomic.
> When switching the order to delete/add the modification works!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
