Return-Path: 
 <dev-return-20008-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 18621 invoked from network); 8 Jul 2007 21:48:36 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 8 Jul 2007 21:48:36 -0000
Received: (qmail 63766 invoked by uid 500); 8 Jul 2007 21:48:38 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 63732 invoked by uid 500); 8 Jul 2007 21:48:37 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 63721 invoked by uid 99); 8 Jul 2007 21:48:37 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Jul 2007 14:48:37 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Received: from [212.27.42.35] (HELO smtp5-g19.free.fr) (212.27.42.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Jul 2007 14:48:34 -0700
Received: from [192.168.0.1] (vol75-3-82-66-216-176.fbx.proxad.net
 [82.66.216.176])
	by smtp5-g19.free.fr (Postfix) with ESMTP id 26AAC40EC8
	for <dev@directory.apache.org>; Sun,  8 Jul 2007 23:48:13 +0200 (CEST)
Message-ID: <46915B9C.8050206@apache.org>
Date: Sun, 08 Jul 2007 23:48:12 +0200
From: Emmanuel Lecharny <elecharny@apache.org>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Simplified server configuration with xbean-spring
References: <A1F184D1-E19D-4766-AFBF-43B3213DB9C6@yahoo.com>
	 <85E95AEF-618F-45CC-9753-FB95498AB289@yahoo.com>
	 <4689991D.4020605@theatlantis.net>
	 <64AC6D58-08DF-40D1-B8A9-589DBF922047@yahoo.com>
	 <43b026c70707021900v1837492bte1981c6b1d65532b@mail.gmail.com>
 <d45b08f00707022055r5cfd9139r89d66ef2bf7afeb6@mail.gmail.com>
 <468DD91D.1050503@ScheduleWorld.com>
In-Reply-To: <468DD91D.1050503@ScheduleWorld.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org

Mark Swanson a écrit :

> Emmanuel Lecharny wrote:
> <snip/>
> Still catching up -- working backwards... wrt the "problems"
>
> 1. I disagree that this file is complex. It's straightforward, simple, 
> and sensible. Perhaps more docs would make it easier for folks but 
> come on, this is light years ahead of other LDAP configs. This _small_ 
> XML config file is a _single_ file. I like it.
>
> Create a simple howto with samples on how to configure it for the most 
> common use cases. Just enable folks to copy/paste the common config 
> options.


Well, from your poit of view, as a experienced user, yes, the current 
server.xml is not too complex. But :
- for new commers, it's quite difficult to get in (and I must admit that 
Dave has a point ith XSchema)
- and the current configuration won't reflect the next level of 
configuration we will reach when all what we want to add into the server 
will be done.

>
> 2. Please _PLEASE_ DO NOT put config info into ADS. Do NOT make me use 
> a GUI tool to configure ADS.  I can't always make an X connection to 
> an ADS machine and it would be a lot of trouble to map and route 
> specific ports in front of the virtual IP router to manage specific 
> ADS instances from port 389. I really like being able to edit the XML 
> file with a text editor.

We will put the config into ADS _and_ you won't have to use a GUI to 
configure the server :). Open Ldap works exactly the wame way, using 
LDIF fiels to modify the configuration. Obviously, this is quite a good 
solution.

Anyway, we won't be able to please all the users ... But having the 
configuration into the server will help a lot when dealing with 
replicated servers (no need to login on N servers, we will have a way to 
'replicate' the configuration)

Emmanuel