Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 48472 invoked from network); 4 Dec 2006 10:57:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Dec 2006 10:57:22 -0000 Received: (qmail 69857 invoked by uid 500); 4 Dec 2006 10:57:30 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 69823 invoked by uid 500); 4 Dec 2006 10:57:29 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 69812 invoked by uid 99); 4 Dec 2006 10:57:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 02:57:29 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ersin.er@gmail.com designates 64.233.162.238 as permitted sender) Received: from [64.233.162.238] (HELO nz-out-0102.google.com) (64.233.162.238) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 02:57:18 -0800 Received: by nz-out-0102.google.com with SMTP id i28so1669855nzi for ; Mon, 04 Dec 2006 02:56:57 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ORoSMibE+VEgeUXVvhZwRtShwoqqLbB4RMz7GwpL/MZ6sW58uLQuYNw6uvAQvj13Zg6+O1b9ZNyhEJe1pt0JVlI92oB+HTK4jQoYINQvFdK92a7iDSsA7RNib5vLGi6COevIyx9kctkrHQmLW1bvMOqpHWyCGxQbVEyxI6eslO8= Received: by 10.65.224.11 with SMTP id b11mr11912260qbr.1165229817363; Mon, 04 Dec 2006 02:56:57 -0800 (PST) Received: by 10.64.48.18 with HTTP; Mon, 4 Dec 2006 02:56:57 -0800 (PST) Message-ID: Date: Mon, 4 Dec 2006 12:56:57 +0200 From: "Ersin Er" To: "Apache Directory Developers List" Subject: Re: [ApacheDS] Schema Subsystem Redesign Objectives In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25155_22147233.1165229817330" References: <456DD538.3020705@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_25155_22147233.1165229817330 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I have added information about the defaultDestinationSchema attribute and clarified the state of destinationSchema attribute wrt it. http://cwiki.apache.org/DIRxSRVx11/schema-subsystem-redesign.html On 11/29/06, Ersin Er wrote: > > On 11/29/06, Alex Karasulu wrote: > > Hi guys, > > > > We have the design in mind and it looks good. Now it's time to start > > the work. I cannot see the whole path to get this done but here's what > > I see into the next few weeks. > > > > 1a). We need to implement a meta schema to represent schema entities as > > entries in the server under ou=schema area. Emmanuel already started on > > this. > > > > 1b). We need parsers for interchanging LDAP description formats for > > schema entities into Schema objects. Ersin already started working on > > these parsers. > > > > 1a and 1b are concurrent. > > > > 2). Need to write the special partition for ou=schema which uses a > > subset of schema information to bootstrap itself and initialize the > > schema subsystem. > > > > 3). Write the schema subsystem facade and initialization code to load > > all entities into their respective registries. Also need to figure out > > how to maintain and access registries for specific SAAs. Basically we > > need a method to lookup a registry based on DN. This will find the SAA > > associated with the DN, and lookup the associated registries with that > SAA. > > > > 4a). Start writing code to inject subschemaSubentry attributes into > > entries falling under SAAs defined by the subtree specifications of > > schema subentries. > > FYI, this has already been implemented in the SubentryService (by Alex > mostly). I may add a few tests to make it sure it works correctly. > > > 4b). Need to start working on virtualization code that injects schema > > description attributes into schema subentries. > > > > 4a and 4b are concurrent. > > > > 5) Rewrite schema checking code to properly apply schema information to > > changes to DIT and respond accordingly. We will use the full LDAP > > schema capabilities to contrain and manage the DIT. > > > > Right now this is as far as I can foresee in terms of general steps. > > > > Regards, > > Alex > > > > > > > > > -- > Ersin > -- Ersin ------=_Part_25155_22147233.1165229817330 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,

I have added information about the defaultDestinationSchema attribute and clarified the state of destinationSchema attribute wrt it.

http://cwiki.apache.org/DIRxSRVx11/schema-subsystem-redesign.html


On 11/29/06, Ersin Er <ersin.er@gmail.com > wrote:
On 11/29/06, Alex Karasulu <akarasulu@apache.org > wrote:
> Hi guys,
>
> We have the design in mind and it looks good.  Now it's time to start
> the work.  I cannot see the whole path to get this done but here's what
> I see into the next few weeks.
>
> 1a). We need to implement a meta schema to represent schema entities as
> entries in the server under ou=schema area.  Emmanuel already started on
> this.
>
> 1b). We need parsers for interchanging LDAP description formats for
> schema entities into Schema objects.  Ersin already started working on
> these parsers.
>
> 1a and 1b are concurrent.
>
> 2). Need to write the special partition for ou=schema which uses a
> subset of schema information to bootstrap itself and initialize the
> schema subsystem.
>
> 3). Write the schema subsystem facade and initialization code to load
> all entities into their respective registries.  Also need to figure out
> how to maintain and access registries for specific SAAs.  Basically we
> need a method to lookup a registry based on DN.  This will find the SAA
> associated with the DN, and lookup the associated registries with that SAA.
>
> 4a). Start writing code to inject subschemaSubentry attributes into
> entries falling under SAAs defined by the subtree specifications of
> schema subentries.

FYI, this has already been implemented in the SubentryService (by Alex
mostly). I may add a few tests to make it sure it works correctly.

> 4b). Need to start working on virtualization code that injects schema
> description attributes into schema subentries.
>
> 4a and 4b are concurrent.
>
> 5) Rewrite schema checking code to properly apply schema information to
> changes to DIT and respond accordingly.  We will use the full LDAP
> schema capabilities to contrain and manage the DIT.
>
> Right now this is as far as I can foresee in terms of general steps.
>
> Regards,
> Alex
>
>
>


--
Ersin



--
Ersin ------=_Part_25155_22147233.1165229817330--