Re: Errors in diradmin-1.6.0

Mike Jackson <[email protected]> writes:

> Dieter Kluenter wrote:
>
>> I'm quite aware of the enheritage problem with structural object
>> classes. There are two solutions to this, either design a new subclass
>> and include a host attribute, or use the extensibleObject object class
>> and apply the host attribute (RFC 2252). I personally quite often make
>> use of the class extensibleObject.
>
> IMO, the extensibleObject object class should be used only in
> temporary situations (e.g. during development where the schema writer
> is not the same person as the application coder). It is basically the
> same as turning schema checking off for those objects which contain
> it. If it were up to me, LDAP servers would not even include
> functionality to run without schema checking, including
> extensibleObject.

RFC-2252,section 7.1 describes extensibleObject, and it is not
mentioned there, that this class should only by used in temporary
situations.If you design aliases for example, you have to include
objectclass extensibleObject in order to define at least the
attribute cn or uid, as the structural objectclass alias includes
only one attribute, which is aliasedObjectName. I could give a few
more examples, where extensibleObject is needed.
As extensibleObject is only an auxiliary objectClass, the requirement
for schema checking is not disabled.

-Dieter

-- 
Dieter Klünter | Systemberatung
http://www.dkluenter.de
GPG Key ID:01443B53



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt