Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <45F99BD0.1020002@verticon.com>
Date: Thu, 15 Mar 2007 14:17:36 -0500
From: "John E. Conlon" <jconlon@verticon.com>
Reply-To: jconlon@verticon.com
Organization: Verticon, Inc.
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [SASL] SASL configuration
References: <568753d90703121820n76021567m551e604a1f6031c7@mail.gmail.com>
 <45F6AEFE.7000904@gmail.com>
In-Reply-To: <45F6AEFE.7000904@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Configurations are such a pain. Properties files, Spring configurations, 
(OSGi configuraiton admin) etc...

Perhaps a future thread with topic [Configuration] would make sense.
Right now as I am typing I have the EMF book opened up on my lap...

cheers,
John

Ole Ersoy wrote:
> Hey Enrique,
>
> This is slightly OT (Off Thread), but still in a remote vicinity 
> somewhere.
>
> John was wondering a while back whether it made sense to load ApacheDS
> and related configuration files using EMF, in the interested of 
> generating
> Eclipse Plugin Editors for editing configuration files and straight 
> forward refactoring and versioning
> of configuration file schemas.
>
> If we want to add/remove configuration elements/attributes we simply 
> update the Ecore model,
> and regenerate and it's done.  All the editors, etc. are automatically 
> updated.  We could also
> create an editor similar to the Eclipse plugin.xml editor, that has 
> tabs for various configuration files
> very easily with this type of approach.
>
> EMF also supports demand loading of proxy references.  This means that 
> if we wanted
> to we could access all configuration information through one central 
> model, but the
> configuration information is still maintained in separate files.  Each 
> file is demand
> loaded when configuration information contained in a proxy reference 
> is requested.
>
> Anyways, just thought I'd mention it for awareness and in case you 
> think it might come in handy
> while reviewing the configuration topology.
>
> Cheers,
> - Ole
>
>
> Enrique Rodriguez wrote:
>> I looked at the way ApacheDS does Spring config, the relationship with
>> the daemon code, etc., and I'm ready to start in on configuration for
>> SASL.  What I'd like to do is create a bean for the LDAP protocol
>> provider that resides in the protocol-ldap module, maybe named
>> LdapProtocolConfiguration.  This would contain the SASL parameters and
>> I could also move over the 3 properties that are used by the LDAP PP
>> from the ServerStartupConfiguration:
>>
>> maxSizeLimit
>> maxTimeLimit
>> isAllowAnonymousAccess
>>
>> WDYT?
>>
>> Enrique
>>
>
>
>