You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2009/08/05 16:25:14 UTC
[jira] Created: (DIRSERVER-1394) Modifying subschema subentry
doesn't work in some case
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, 1.5.5
Reporter: Stefan Seelmann
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.
[jira] Closed: (DIRSERVER-1394) Modifying subschema subentry
doesn't work in some case
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Ayyagari closed DIRSERVER-1394.
-------------------------------------
Resolution: Cannot Reproduce
Assignee: Kiran Ayyagari
Not able to reproduce this, should have been fixed as part of DIRSERVER-1393, closing.
> 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
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> 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.
[jira] Updated: (DIRSERVER-1394) Modifying subschema subentry
doesn't work in some case
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DIRSERVER-1394) Modifying subschema subentry
doesn't work in some case
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1394:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> 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: 2.0.0-RC1
>
>
> 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.