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: pass (asf.osuosl.org: domain of enriquer9@gmail.com designates
 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:reply-to:organization:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:from;
        b=jwt7n/q5kqG4fZQ2vNgRAfIozVZ+Yw951NVJEBd+B62XVm2hQoK5WDKRbT9SbGl8Fs21Z76yFMvJBtkkWVBBvpsw1RFzzmroWUCj85FHWNZIaDPnQ5HFZ98O2nHeollVndgmJCMFS23EG58Ck0bTVBpjalZobnLAj58aUbpIJVI=
Message-ID: <4416E6C4.4040904@apache.org>
Date: Tue, 14 Mar 2006 10:52:36 -0500
Reply-To: erodriguez@apache.org
Organization: Apache Software Foundation
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [OSGi] Configuration Admin Service
References: <1134577017.4073.98.camel@trout>
  <43A734B1.9020708@apache.org>	 <1135038335.4073.45.camel@trout>
  <43A887E4.3050507@apache.org>	 <1135187521.4071.113.camel@trout>
  <43B41D80.2060907@apache.org> <1136219244.4072.9.camel@trout>
In-Reply-To: <1136219244.4072.9.camel@trout>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
From: Enrique Rodriguez <enriquer9@gmail.com>

John E. Conlon wrote:
> On Thu, 2005-12-29 at 11:31, Enrique Rodriguez wrote:
> 
>>Great.  Again, I don't know your use case.  BTW, the config admin 
>>service isn't totally done:  not all of the store ops work.  I'd love 
>>some help here; their impl should be straightforward, I just have only 
>>done the ones I need.
>>
> 
> How can I help?

I figure you can check out and review the OSGi work on Directory 1.1 or 
pitch in on the use of CM for what is currently in the XML config.  Or 
help in moving CM, Prefs, and UA over to Felix.  They'll need an M2 
update, basic dep updates (refactoring, renaming packages), and 
eventually updates to be R4-compliant.  Also, not all of the 
directory-backed CM store was implemented; I only did what I needed to 
make directory work.  Patches here would be great.

> How will you provide for attributes that have multiple values, like
> objectClasses?

While they are returned by JNDI, I believe CM will ignore them.  If this 
is outside the scope of CM then there isn't much we can do.  Multiple 
values in config is typically on one line which gets tokenized.  This is 
how I would do a multi-value, for example Kerberos encryption types; put 
them in the DIT as one long string.  Or now, that I think about it, they 
could be multi-valued in the DIT and converted to one-line strings by 
the CM and parsed by the receiving service?  WDYT?

Enrique