From dev-return-7750-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Wed Sep 07 00:13:13 2005 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 87735 invoked from network); 7 Sep 2005 00:13:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Sep 2005 00:13:11 -0000 Received: (qmail 70232 invoked by uid 500); 7 Sep 2005 00:13:11 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 70192 invoked by uid 500); 7 Sep 2005 00:13:10 -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 70179 invoked by uid 99); 7 Sep 2005 00:13:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2005 17:13:10 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_POST,FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of aok123@bellsouth.net designates 205.152.59.65 as permitted sender) Received: from [205.152.59.65] (HELO imf17aec.mail.bellsouth.net) (205.152.59.65) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2005 17:13:21 -0700 Received: from ibm57aec.bellsouth.net ([65.80.200.112]) by imf17aec.mail.bellsouth.net with ESMTP id <20050907001306.IFTL17957.imf17aec.mail.bellsouth.net@ibm57aec.bellsouth.net> for ; Tue, 6 Sep 2005 20:13:06 -0400 Received: from [172.16.1.152] (really [65.80.200.112]) by ibm57aec.bellsouth.net with ESMTP id <20050907001306.MMOH15611.ibm57aec.bellsouth.net@[172.16.1.152]> for ; Tue, 6 Sep 2005 20:13:06 -0400 Message-ID: <431E3091.4090700@bellsouth.net> Date: Tue, 06 Sep 2005 20:13:05 -0400 From: Alex Karasulu User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: dynamic schema support References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Norbet Reilly wrote: > Hi DS-ers, Hello! > My immediate concern is supporting a custom back-end LDAP partition > which has its own schema, prior to the availability of RFC 3672 > support (which sounds like it will smooth the way in the future). It sure will. You'll be able to define an autonomous administrative point for the context of your partition to manage all the aspects of the DIT therein. > I have plugged in my custom LDAP AbstractContextPartition successfully > (using the IETF LDAP classes to convert JNDI back to LDAP) and have > written some support classes which fetch the remote > org.ietf.ldap.LDAPSchema (during doInit() using some credentials known > from the partition's configuration properties) and internalise it into > the org.apache.ldap.server.schema.GlobalRegistries instance (noting in > the future AbstractBootstrapProducer should ideally inherit from an > abstract intermediate class to ease writing of classes like mine which > create non-bootstrap instances of classes extending > AbstractAttributeType/AbstractSchemaObject etc) . ...what a sentence... Made sense to me. > My question is: what is the best way to get the ApacheDS server's > org.apache.ldap.server.schema.SchemaService to notice that additions > have been made to the GlobalRegistries. Nothing like this so far. Really the schema subsystem is extremely primitive. In fact we never intended to use the boostrap mechanism for anything other than supporting some critical schema elements for the system partition. Now we're using the bootstrap mechanism for the whole shebang. Part of this is my fault. I waited until 3672 came since this would give me the opportunity to really think about doing schema the right way. > I notice the addition of AddContextPartitionConfiguration in ApacheDS > 0.9.2, but I'm not sure hwo to configure its use via an ApacheDS > configuration file (or even if it is indeed the answer to my problems). Nah this is something else totally. It's for dynamically adding and removing partitions after system startup. > Failing that the only other approach I can think of is to get the > startup infrastructure to create a back-end InitialContext very early > so that my custom partition is queried for its schema just after the > bootstrap schemas are processed, which sounds a very experimental path > to follow. Yeah you're not in a very good situation actually. There really is no clean way to solve your problem. We just need to implement the Schema subsystem properly. You interested in giving that a try? > Note that attempting to refresh the schema via JXplorer never seems to > have any effect (I imagine that somewhere in the server it is assumed > that there are only bootstrap schemas). You guessed right ... schema is static on startup. > > Any guidance would be very much appreciated! Sorry can't really give you a better way here other than to build out the schema subsystem so it can support your needs. This means just implementing it properly. There is no other trick we can use at the moment. Alex