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: <1934496616.1124902696841.JavaMail.jira@ajax.apache.org>
Date: Wed, 24 Aug 2005 18:58:16 +0200 (CEST)
From: "Alex Karasulu (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIREVE-195) Complete support for most schema
 checking constructs
In-Reply-To: <1964674513.1122570502644.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DIREVE-195?page=all ]

Alex Karasulu updated DIREVE-195:
---------------------------------

    Fix Version: 0.9.3
      Assign To:     (was: Alex Karasulu)

> Complete support for most schema checking constructs
> ----------------------------------------------------
>
>          Key: DIREVE-195
>          URL: http://issues.apache.org/jira/browse/DIREVE-195
>      Project: Directory Server
>         Type: New Feature
>     Reporter: Enrique Rodriguez
>      Fix For: 0.9.3

>
> Everything is in place for schema checking but nothing exists today.  The reason being Alex did not waste time on schema subsystem since it would need to be revamped once we implemented subentries.  Subentries for schema AAAs would store the schema info there rather than having one schema for the entire DIT mastered by a DSA.  Basically an interceptor for schema management would use the subentry information to check for correct schema usage in different schema AAAs in the DIT.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira