directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <>
Subject Pb with Schema Object names collision
Date Tue, 18 Aug 2009 14:33:31 GMT
RFC 4512 stipulates that Schema Objects names are case insensitives and 
can collide (ie, we can use the same name for an AT and an OC, for 
instance) :

RFC 4512, 6.2 :
Implementations MUST be prepared that the same short name might be
   used in a subschema to refer to the different kinds of schema
   elements. That is, there might be an object class 'x-fubar' and an
   attribute type 'x-fubar' in a subschema.

We have filed two JIRAs about it 

As I'm reviewing the OidRegistry code, as a follow up of the multiple 
Schema problems, I found that :

in cosine Schema :
attributetype ( 0.9.2342.19200300.100.1.55 NAME 'audio'

// RFC 2252, removed in RFC 4517
String AUDIO_SYNTAX                           = 

in SystemSyntaxProducer :

        syntax = new BootstrapSyntax( SchemaConstants.AUDIO_SYNTAX, 
syntaxCheckerRegistry );
        syntax.setNames( new String[]
            { "Audio" } );
        syntax.setHumanReadable( false );
        cb.schemaObjectProduced( this, syntax.getOid(), syntax );

the byName() method in the oidRegistry will have the audio name pointing 
to 2 different OIDs, which is not allowed, as the name is expected to be 
case insensitive ...

We have to change the way the OIDs are registred, so that the lookup done in this registry
is using the SchemaObject type we are looking for (we always know what kind of SchemaObject
we are looking for).

cordialement, regards,
Emmanuel L├ęcharny

View raw message