Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 75890 invoked from network); 9 Jul 2007 21:31:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jul 2007 21:31:20 -0000 Received: (qmail 3785 invoked by uid 500); 9 Jul 2007 21:31:22 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 3739 invoked by uid 500); 9 Jul 2007 21:31:22 -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 3728 invoked by uid 99); 9 Jul 2007 21:31:22 -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 14:31:22 -0700 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 akarasulu@gmail.com designates 64.233.162.235 as permitted sender) Received: from [64.233.162.235] (HELO nz-out-0506.google.com) (64.233.162.235) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jul 2007 14:31:18 -0700 Received: by nz-out-0506.google.com with SMTP id o1so694799nzf for ; Mon, 09 Jul 2007 14:30:58 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=uey1Kt0BzGPXIFzolBEPDPM9VvZH6iPcJCBkxTBv1BoGJyvfT7rB98erS50/cE1zua5oYKz/Ic0LnIbW2PmCNqDE35iJpQTMz+makbav+4JdrakXZeUSjUXInPwA2BEQn4tc8mhBpj7zPdmRQsrEy0U9Ptk2d78/JV/oFTpybk4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=KdIYfwZnLVU+JJQMG691rHX/5AGjZ4PKSSYY0RtxL3Gjw53ZGMvj21QhLoSNXpC3qurYf0yg9I0xTPY13bNj8fbtKs5lvGnGj1p4SiB4442zjg1GUe2ooFsqtot3kKNbg/Qowde7WnewkYnVCtEUcG76JHPKf1XOmF2uXIA8dLs= Received: by 10.142.90.8 with SMTP id n8mr260161wfb.1184016657288; Mon, 09 Jul 2007 14:30:57 -0700 (PDT) Received: by 10.142.77.21 with HTTP; Mon, 9 Jul 2007 14:30:57 -0700 (PDT) Message-ID: Date: Mon, 9 Jul 2007 17:30:57 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: Simplified server configuration with xbean-spring In-Reply-To: <46928A76.8060104@ScheduleWorld.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_165038_26062349.1184016657231" 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> <46928A76.8060104@ScheduleWorld.com> X-Google-Sender-Auth: 0e17d87549906b0b X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_165038_26062349.1184016657231 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Fair enough. We can still allow for XML based configuration files in addition to alternative methods. Perhaps we can push the use of such a mechanism to be based on an optional system parameter. Alex On 7/9/07, Mark Swanson wrote: > > 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. > ------=_Part_165038_26062349.1184016657231 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Fair enough.  We can still allow for XML based configuration files in addition
to alternative methods.  Perhaps we can push the use of such a mechanism
to be based on an optional system parameter. 

Alex

On 7/9/07, Mark Swanson <mark@scheduleworld.com> wrote:
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:

<quote>
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.
</quote>

<b> +1 </b>

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.

------=_Part_165038_26062349.1184016657231--