speedy zinc wrote:
Create a new structural objectclass called MyRole - it will extend nsRoleDefinition and include the myWackyAttr attribute (as a MAY preferably, not a MUST). Then, you'll have to create MyRole roles, for which there is also not console support.Ok, I have this weird idea that I want to make a new attribute an allowed attribute of an existing objectclassand all its sub-classes, but without modifying the definition of the existing class, only thru extension.For example, if I define a new attribute called "myWhackyAttr", and I want to make it part of anallowed attribute of nsRoleDefinition (or nsSimpleRoleDefinition), so that the attribute is available to all sub-classes. To do that, I can change the definition of nsRoleDefinition in 00core.ldif, which everyone would say "stop right there,you shouldn't do that".The other way is, I can create an aux objectclass with that attribute, and everytime I create a new role, I have to make sure that I add that object class to the new entry. That's tedious, and might forget it. Is there a third way to enforce that?
thanks for any hint. sz__________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users