11:52 p.m.
Hello all,
I derive an objectClass from organizationalUnit and make it AUXILIARY. I am
getting this error
Can any one please explain , me why this error comes
user-defined ObjectClass has inappropriate SUPerior
Thanks in advance,
Arunachalam
****************************************************************************
****************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
3:31 p.m.
Arunachalam Parthasarathy wrote:
Hello all,
I derive an objectClass from organizationalUnit and make it AUXILIARY.
I am getting this error
Can any one please explain , me why this error comes
user-defined ObjectClass has inappropriate SUPerior
You probably aren't loading core.schema first.
--
Kind Regards,
Gavin Henry.
Managing Director.
T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
E ghenry(a)suretecsystems.com
Open Source. Open Solutions(tm).
http://www.suretecsystems.com/
3:51 p.m.
Gavin Henry wrote:
Arunachalam Parthasarathy wrote:
> Hello all,
>
> I derive an objectClass from organizationalUnit and make it
> AUXILIARY. I am getting this error
>
> Can any one please explain , me why this error comes
>
> user-defined ObjectClass has inappropriate SUPerior
>
>
>
You probably aren't loading core.schema first.
organizationalUnit is STRUCTURAL; you can't make AUXILIARY a class
derived from a STRUCTURAL one.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
3:54 p.m.
Pierangelo Masarati wrote:
Gavin Henry wrote:
> Arunachalam Parthasarathy wrote:
>> Hello all,
>>
>> I derive an objectClass from organizationalUnit and make it
>> AUXILIARY. I am getting this error
>>
>> Can any one please explain , me why this error comes
>>
>> user-defined ObjectClass has inappropriate SUPerior
>>
>>
>>
> You probably aren't loading core.schema first.
organizationalUnit is STRUCTURAL; you can't make AUXILIARY a class
derived from a STRUCTURAL one.
Thanks for that reminder...I should go to sleep now!
Gavin.
2:03 a.m.
On Saturday 29 September 2007 08:52:18 Arunachalam Parthasarathy wrote:
Hello all,
I derive an objectClass from organizationalUnit and make it AUXILIARY. I
am getting this error
Can any one please explain , me why this error comes
user-defined ObjectClass has inappropriate SUPerior
There's no reason to derive an AUXILIARY from a STRUCTURAL anyway. Derive your
AUXILIARY from top, or make it STRUCTURAL and derive from a STRUCTURAL.
Regards,
Buchan
2:42 a.m.
Hello all,
> I derive an objectClass from organizationalUnit and make it
AUXILIARY. I
> am getting this error
>> Can any one please explain , me why this error comes
>> user-defined ObjectClass has inappropriate SUPerior
There's no reason to derive an AUXILIARY from a STRUCTURAL anyway.
>Derive
your
AUXILIARY from top, or make it STRUCTURAL and derive from a
STRUCTURAL.
Regards,
Buchan
Hello Buchan,
Thanks for the reply.
1) Second choice of making new objectClass STRUCTURAL is fine for me , but
will there be any restrictions for new STRUCTURAL object classes to be
created from any parent (for instance, organizationalUnit)
And from this, new STRUCTURAL class, if I derive one more hierarchy down ,
will there be any restrictions for that grand child object class.
2) Can I know why is that restriction that AUXILIARY cannot be derived from
STRUCTURAL?
Thanks in advance,
Arunachalam.
****************************************************************************
****************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
6:49 a.m.
1) Second choice of making new objectClass STRUCTURAL is fine for me
,
but will there be any restrictions for new STRUCTURAL object classes
to be created from any parent (for instance, organizationalUnit)
Only that they be STRUCTURAL.
And from this, new STRUCTURAL class, if I derive one more hierarchy
down , will there be any restrictions for that grand child object
class.
None beyond what apply to all object classes. Proprietary/custom schema
is treated no differently than standard schema.
2) Can I know why is that restriction that AUXILIARY cannot be
derived
from STRUCTURAL?
Because it makes no sense. Look-up the meanings of AUXILIARY and
STRUCTURAL.
--
Adam Tauno Williams, Network & Systems Administrator
Consultant - http://www.whitemiceconsulting.com
Developer - http://www.opengroupware.org
3:49 a.m.
Adam Tauno Williams wrote:
Because it makes no sense. Look-up the meanings of AUXILIARY and
STRUCTURAL.
See RFC 4512 "Lightweight Directory Access Protocol (LDAP): Directory
Information Models".
Citing from section 2.4.3:
"Auxiliary object classes cannot subclass structural object classes."
Ciao, Michael.
--
Michael Ströder
E-Mail: michael(a)stroeder.com
http://www.stroeder.com
5816
days inactive
5838
days old
openldap-software@openldap.org
7 comments
6 participants
participants (6)
-
Adam Tauno Williams -
Arunachalam Parthasarathy -
Buchan Milne -
Gavin Henry -
Michael Ströder -
Pierangelo Masarati