You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Introduction

Apache DS has to keep a lot of internal structures available from all the parts of the server. This is done through what we call  Registries. We have many kind of Registries :

  • OID Registry : it stores a relation between object names and the associated OID.
  • ObjectClass Registry : it stores all information related to ObjectClasses
  • <to be continued>

A very important point is that all those registries are just objects used to ease the navigation through the different elements tha server is using. The central point is the OID object.

If we focus on ObjectClass and AttributeType, then we will need to use this hierarchy :

 

AttributeType hierarchy

The AttributeType classHierarchy is shown in the following picture :

We don't represent the existing hierarchy, which includes some more classes, separated in an AbstractAttributeType class and 4 implementation, into Producer classes, because I don't think it fits the need. We should just have one concrete implementation, and no abstract classes, as we will not extend the AttributeTypes in any way.

Those classes will be removed :

  • AttributeTypeImpl
  • BootstrapAttributeType
  • ConcreteSchemaAttributeType

ObjectClass Hierarchy

The ObjectClass hierarchy is pretty much the same, with some different attributes.

Syntax object

The syntx object is used to check that attributes are correctly formatted when submitted by a user. For instance, the Bit String syntax is '00101...(0|1)*...1011'B and we must check that the given attribute value respect this syntax. The RFC 4517 list 34 different syntaxes to be implemented.

Here is the hierarchy for this kind of object :

  • No labels