Hi Stefan,
it's good to see you back :) I guess you were pretty busy with day job ...
On 4/16/07, Stefan Zoerner <stefan@labeo.de> wrote:
>
> Hi all!
>
> I found some time to test the new schema sub system of ApacheDS 1.5 and
> I am really impressed how nice it works.
>
> During some additions of new attribute types and object classes, I found
> a behavior for which I am not sure whether it is an error: I was able to
> add a new object class and a new attribute type with the same OID value.
Sounds bad :(
I used an LDIF import to extend my schema, my attribute type for
> instance looked like this (just a test OID used):
>
> dn: m-oid=9.9.9,ou=attributeTypes,cn=sevenSeasSchema,ou=schema
> m-usage: USER_APPLICATIONS
> m-equality: integerOrderingMatch
> objectClass: metaAttributeType
> objectClass: metaTop
> objectClass: top
> m-name: numberOfGuns
> m-oid: 9.9.9
> m-singleValue: TRUE
> m-description: Number of guns of a ship
> m-collective: FALSE
> m-obsolete: FALSE
> m-noUserModification: FALSE
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.27
>
> Afterwards I added the following objectclass:
>
> dn: m-oid=9.9.9,ou=objectClasses,cn=sevenSeasSchema,ou=schema
> objectClass: top
> objectClass: metaTop
> objectClass: metaObjectclass
> m-supObjectClass: top
> m-oid: 9.9.9
> m-name: ship
> m-must: cn
> m-may: numberOfGuns
> m-may: description
> m-typeObjectClass: STRUCTURAL
> m-obsolete: FALSE
> m-description: A ship
>
> I assumed this should fail (two schema elements with the same OID added
> to the schema). Am I right here? Or is it not allowed to use a plain
> LDIF import to load schema elements? If it is an error, I'll try to
> isolate the problem to several tests and raise a JIRA ...
Yeah, we deserved a JIRA here, I think...
Thanks for having found this nasty bug !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
|