Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 93837 invoked from network); 10 Jan 2007 17:34:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jan 2007 17:34:29 -0000 Received: (qmail 67723 invoked by uid 500); 10 Jan 2007 17:34:35 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 67692 invoked by uid 500); 10 Jan 2007 17:34:35 -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 67681 invoked by uid 99); 10 Jan 2007 17:34:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 09:34:35 -0800 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 64.233.184.231 as permitted sender) Received: from [64.233.184.231] (HELO wr-out-0506.google.com) (64.233.184.231) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 09:34:25 -0800 Received: by wr-out-0506.google.com with SMTP id 57so110003wri for ; Wed, 10 Jan 2007 09:34:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:organization:user-agent:mime-version:to:subject:references:in-reply-to:content-type:sender; b=FzwrVjESbYHkDmAKW4VyAcoeu/DVxIO6MCkPkWAqExzvoVYPgaCvpErWWRpqP/2Qb7RYtbiA6nwYeiJlhH0UZ1p+Y0gGXFEl4sUBolnnmuXBLvFutLo/8xqNKjQSKZ0xqR5j9k5Iis8H9E/JNK6C3q7Ij53JIcwd3/blvQ9GmN8= Received: by 10.90.84.17 with SMTP id h17mr429235agb.1168450444525; Wed, 10 Jan 2007 09:34:04 -0800 (PST) Received: from ?172.16.1.7? ( [65.80.200.112]) by mx.google.com with ESMTP id 43sm51191737wri.2007.01.10.09.34.03; Wed, 10 Jan 2007 09:34:04 -0800 (PST) Message-ID: <45A523C9.6040904@apache.org> Date: Wed, 10 Jan 2007 12:35:05 -0500 From: Alex Karasulu Reply-To: akarasulu@apache.org Organization: Apache Software Foundation User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Reducing the complexity/verbosity of default server.xml (and custom configuration files) References: <45A3E975.5000007@labeo.de> In-Reply-To: <45A3E975.5000007@labeo.de> Content-Type: multipart/mixed; boundary="------------050305090608000402060606" Sender: Alex Karasulu X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------050305090608000402060606 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Stefan Zoerner wrote: > Hi all! > > There is some criticism about configuration complexity of ApacheDS, > especially from people who argue after a first glance at it. The > verbosity is mostly driven by the Spring Framework. > > Here are three ideas I had: > > --- > 1) Simplify default server.xml by using another property setting style > > Currently, the server.xml seems to favor this style (example): > ... > > system > 100 > ou=system > ... > > Is there any reason why not to use this style: > ... > > > > > ... Don't know if it will work with spring. Try it in a working ADS installtion and run your experiment to see. If it works I like this reduction in noise. > (quite easy to achieve. I volunteer, if nobody contradicts that this is > a (rather small) imrovement) > --- > > 2) Reduce length of partition configuration > > Currently, partition configuration are very long, mostly because of the > many many indices for internal attributes: Yeah you don't need to do an index for it. It can be defaulted. > ... > class="org.apache.directory.server.core.partition.impl.btree.MutableIndexConfiguration"> > > name="attributeId">1.3.6.1.4.1.18060.0.4.1.2.1 > 100 > > (many others follow, in each partition the same > ... > > If it is highly recommend to use these indices, how about having a > special IndexConfiguration as a default, which only has to be extended > in order to adjust it to your needs? Good idea I think we may already have this but I must confirm it. > --- > > 3. Define our own tags for configuration with the help XML Schema-based > configuration introduced in Spring 2.0. This is more a long term option. > But I think the idea is promising. > > What do you think? Hmmm I don't even know what this is. I don't have any ideas on Spring 2.0. But from what I can gather from your question above it does sound like a nice solution to use a custom ads schema. Regards, Alex --------------050305090608000402060606 Content-Type: text/x-vcard; charset=utf-8; name="akarasulu.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="akarasulu.vcf" begin:vcard fn:Alex Karasulu n:Karasulu;Alex org:Apache Software Foundation;Apache Directory adr:;;1005 N. Marsh Wind Way;Ponte Vedra ;FL;32082;USA email;internet:akarasulu@apache.org title:Member, V.P. tel;work:(904) 791-2766 tel;fax:(904) 808-4789 tel;home:(904) 808-4789 tel;cell:(904) 315-4901 note;quoted-printable:AIM: alexokarasulu=0D=0A= MSN: aok123@bellsouth.net=0D=0A= Yahoo!: alexkarasulu=0D=0A= IRC: aok=0D=0A= PGP ID: 1024D/4E1370F8 BBCC E8D8 8756 2D51 C3D4 014A 3662 F96F 4E13 70F8=0D=0A= x-mozilla-html:FALSE url:http://people.apache.org/~akarasulu version:2.1 end:vcard --------------050305090608000402060606--