Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 3410 invoked from network); 19 Sep 2007 14:18:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Sep 2007 14:18:57 -0000 Received: (qmail 7266 invoked by uid 500); 19 Sep 2007 14:18:48 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 7217 invoked by uid 500); 19 Sep 2007 14:18:47 -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 7174 invoked by uid 99); 19 Sep 2007 14:18:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 07:18:47 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com designates 66.249.82.231 as permitted sender) Received: from [66.249.82.231] (HELO wx-out-0506.google.com) (66.249.82.231) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 14:18:44 +0000 Received: by wx-out-0506.google.com with SMTP id s8so147720wxc for ; Wed, 19 Sep 2007 07:18:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=VxbmxUsU4VZbQ+JC/E9e9y5SoEc0V4ESPgEx1G5XgGg=; b=C//knBjCG9amqauBAdbI+5SXItWTNqzcmqMK4lCSZS7oSS1GBEVlKNCf5DVnNjYkDdmqTWnyvuHPANcwTDlt2f5PtGHSckPo2zR/c7XuyKLgE19sq3DX12+Cr4ZU2bMkxYUJOpy+OHBWDkuGCCB4x5QDWkGo2vxUJv/Hv6V4AVE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=grWwWLt7rvLrQIC719euW/dwyygibK0sf2GkARhh7TXfUne2XgDT3/Ta12JkNe+KvQV7+vdteUXXR0oKTflCwv+NIz4Tj3HVLFBC1Wywlp5/LFJLxCqbjiPhQWbSCATZRKxmX86dXnGfoXupDq3FcucL4IKqMQ6j8Bt8zk6P9tg= Received: by 10.90.29.18 with SMTP id c18mr647629agc.1190211503348; Wed, 19 Sep 2007 07:18:23 -0700 (PDT) Received: by 10.90.31.7 with HTTP; Wed, 19 Sep 2007 07:18:23 -0700 (PDT) Message-ID: Date: Wed, 19 Sep 2007 16:18:23 +0200 From: "Emmanuel Lecharny" Reply-To: elecharny@iktek.com To: "Apache Directory Developers List" Subject: Re: Custom Schema - Moving from DS 1.0 to 1.5 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org Ldif files are loaded in the order of appearance in the server.xml file. There is no way to inject some entries before injecting the structure (ie AT and OC), because the new SchemaChecker is really more strict in 1.5 than in 1.0. On 9/19/07, Simon.Temple@saaconsultants.com wrote: > > Thanks Guys > > I think I'm going to use Studio to import our old schema files and conver= t > to LDIF. DS can then load them on first start. > > Can I influence the order of processing of my LDIF files? Otherwise I ma= y > import a file of entries of a type I have yet to define - content before > structure? > > Hope this makes sense... > > - SimonT > > > 19 September 2007 14:11 > To: "Apache Directory Developers List" > cc: > From: "Emmanuel Lecharny" > Subject: Re: Custom Schema - Moving from DS 1.0 to 1.5 > > > Hi Simon, > > you may also want to use JNDI to inject your schema into the server. > This is explained here : > > http://directory.apache.org/apacheds/1.5/add-your-first-elements-to-the-s= chema.html#Addyourfirstelementstotheschema-UsingJNDItoaddtheschemaelementsp= rogrammatically > > Last, not least, you may use the SchemaConverter we have created to > generate some Ldif file from your schema, and then import this ldif > file into the server. Youc an use Apache Studio to generate those ldif > files. > > However, we need more documentation about this aspect. Can you fill a > JIRA asking for more doco about schema loaded into an embedded server > ? > > Thanks ! > > On 9/19/07, David Jencks wrote: > > One way to do this is to use the maven plugin to build your own bootstr= ap > > partition that includes a > > org/apache/directory/server/schema/bootstrap/partition/DBFILES > > and to put that in your server instead of the supplied bootstrap > partition > > jar. An example of this approach is in my copy of triplesec, in > particular > > > https://svn.apache.org/repos/asf/directory/sandbox/djencks/triplesec-jacc= 2/bootstrap-partition. > > Be sure to remove the original bootstrap partition jar or the server > won't > > start. > > > > There may be other ways to do this but I think this is fairly convenien= t > for > > an embedded server. > > > > thanks > > david jencks > > > > > > On Sep 19, 2007, at 6:21 AM, Simon.Temple@saaconsultants.com wrote: > > > > With DS 1.0 we used OpenLdap style schema files from which we created > java > > files using apacheds-core-plugin and maven. > > Then we added them to our configuration using > > MutableServerStartupConfiguration.setBootstrapSchemas(). > > > > How should I generate and install our 20+ custom schema for DS 1.5? > > > > I need to do this programmatically as we deliver DS as part of an > embedded > > solution. > > > > Should I use BootstrapSchemaLoader()? Can someone point me to an examp= le > or > > Wiki on this? > > > > Many Thanks > > > > > > Simon Temple > > > > > > > -- > Regards, > Cordialement, > Emmanuel L=E9charny > www.iktek.com > > --=20 Regards, Cordialement, Emmanuel L=E9charny www.iktek.com