Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 1462 invoked from network); 9 Jul 2007 19:20:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jul 2007 19:20:43 -0000 Received: (qmail 47773 invoked by uid 500); 9 Jul 2007 19:20:45 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 47724 invoked by uid 500); 9 Jul 2007 19:20:44 -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 47706 invoked by uid 99); 9 Jul 2007 19:20:44 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jul 2007 12:20:44 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [72.51.41.97] (HELO ns2.scheduleworld.com) (72.51.41.97) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 09 Jul 2007 12:20:41 -0700 Received: from 10.0.2.93 ([10.0.2.93]) by ns2.scheduleworld.com (JAMES SMTP Server 2.2.1-RC1) with SMTP ID 564 for ; Mon, 9 Jul 2007 15:20:04 -0400 (EDT) Message-ID: <46928A76.8060104@ScheduleWorld.com> Date: Mon, 09 Jul 2007 15:20:22 -0400 From: Mark Swanson User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Simplified server configuration with xbean-spring References: <85E95AEF-618F-45CC-9753-FB95498AB289@yahoo.com> <4689991D.4020605@theatlantis.net> <64AC6D58-08DF-40D1-B8A9-589DBF922047@yahoo.com> <43b026c70707021900v1837492bte1981c6b1d65532b@mail.gmail.com> <468DD91D.1050503@ScheduleWorld.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Alex Karasulu wrote: > Mark keep in mind that you can use command line tools instead of a GUI > to set the configuration of the server when the configuration is in the DIT. > > Furthermore you can just load an LDIF instead of using a server.xml to > setup the initial configuration of the server. So you get the best of both > worlds: a flat configuration file and remote configuration capabilities. > > However we want to make sure we make the configuration interfaces as > easy to use as they were with the server.xml but behind the scenes > different mechanisms will be utilized. All in all it should be much more > plyable. Ok. One more email from me and I will stop being a stick in the mud :-) From what I understand of the command line tools, I assume you are speaking of 'load LDIF into server'? Wrt LDIF - I am sure that the sample ldif file with embedded examples would be more confusing to me, and a GUI/LDAP editor is not going to make this any better. I agree with Norval: Frankly I think XML is a much richer medium to express complex configuration settings as beans, then an LDAP schema which is better suited to modelling much simpler abstractions. +1 The existing configuration process works. Let's leave it at that and if folks want to take the time to build a GUI/alternate config format then please consider creating it as an alternate config/maintenance option. (Even if it was the primary/default option). Cheers. -- http://www.ScheduleWorld.com/ Free Google Calendar synchronization with Outlook, Evolution, cell phones, BlackBerry, PalmOS, Exchange, Mozilla, Thunderbird, Pocket PC/Windows Mobile. Also sync tasks, notes and contacts! WebDAV, vfreebusy, RSS, LDAP, iCalendar, iTIP, iMIP support.