Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <11509786.1187535570748.JavaMail.jira@brutus>
Date: Sun, 19 Aug 2007 07:59:30 -0700 (PDT)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSERVER-851) Check that new objectClasses do
 not have wrong KIND combinations
In-Reply-To: <9282185.1171269425528.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIRSERVER-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520962 ] 

Emmanuel Lecharny commented on DIRSERVER-851:
---------------------------------------------

from RFC 4512 :

STRUCTURAL can inherit from ABSTRACT or STRUCTURAL
ABSTRACT can inherit from ABSTRACT
AUXILIARY can inherit from ABSTRACT or AUXILIARY

STRUCTURAL inheritance tree must ends with an inheritance to the 'top' ABSTRACT class

Which means, as showed in the next example, where --> means 'inherit from', and (XXX)* means 'inherits 0 to N times from the XXX kind', we can have the following inheritance trees :

STRUCTURAL --> (STRUCTURAL)* --> (ABSTRACT)* --> 'top'
AUXILIARY --> (AUXILIARY)* --> (ABSTRACT)* --> 'top'  
ABSTRACT --> (ABSTRACT)* --> 'top'  

> Check that new objectClasses do not have wrong KIND combinations
> ----------------------------------------------------------------
>
>                 Key: DIRSERVER-851
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-851
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.1
>
>
> AUXILIARY, STRUCTURL and ABSTRACT objectClass kind terms in the description may be invalid according to the superClasses they derive from.  For example when extending a structural objectClass you cannot make it abstract.  This presently can happen.  A check is needed to prevent this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.