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 (nike.apache.org: domain of elecharny@gmail.com designates
 74.125.82.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=mE1hJ/5qwgze9/OduNFah4HPMiJDdcY+5oZ0x/olK0lhENWO7BoOPW2Hpno3QEYABN
         9zt6CtvQcs/KLQccXhgr1UPHqmjIlAo/rfaI8UCRGAnUI3sdiAN0tTrAlFS92l4GLL5o
         8fjlfcv9uQ9mI1IZckBHDNz0f+80lafPfksAU=
Message-ID: <4D218EE7.5070203@gmail.com>
Date: Mon, 03 Jan 2011 09:55:03 +0100
From: Emmanuel Lecharny <elecharny@gmail.com>
Reply-To: elecharny@apache.org
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: DnNode class (was :Re: Creation of a second Subentry cache)
References: <4D20471A.60001@gmail.com>
	<53356FC5-0ACF-41B0-83AA-868F8F0A3DC9@gmail.com>	<4D210A6D.7040703@gmail.com>
	<AANLkTinG53+sMYOeKrOMm0xhkNaHex3zq1vkgk02wrmP@mail.gmail.com>
	<4D2111FF.9010404@gmail.com>
	<AANLkTi==EF5nQxEj+Yp8YxEwTd4hngyBeVxo13mOL4B-@mail.gmail.com>
	<4D211BF4.3000703@apache.org>
	<AANLkTik=Y9Hr3JrquJPbb3Pgi6jxj1h3dw6wvzETCC9O@mail.gmail.com>
 <AANLkTimu-Z9R0B23a7ep8SKhGQZRwXvaM9PssrAJCMt6@mail.gmail.com>
In-Reply-To: <AANLkTimu-Z9R0B23a7ep8SKhGQZRwXvaM9PssrAJCMt6@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

(Renamed the thread for clarity)

On 1/3/11 9:40 AM, Stefan Seelmann wrote:
> On Mon, Jan 3, 2011 at 2:27 AM, Alex Karasulu<akarasulu@apache.org>  wrote:
>> Not referring to the SchemaUI bundle. In studio we have all of ApacheDS
>> available in the embedded ApacheDS plugin bundle. This however is not
>> visible outside because it's an OSGi bundle, however there's no reason why
>> the DnNode class cannot be accessed in a similar fashion through the AP UI
>> plugin bundle by having a dependency on core-api.
>> Essentially studio already uses the entire server in the ApacheDS plugin.
> It's not visible because the ApacheDS JARs are not added to the bundle
> classpath. Instead the ApacheDS plugin just extracts the entire server
> to the file system and starts a new java process.
>
>> What's the big deal in having another bundle depend on core-api for managing
>> APs?
> Pierre-Arnaud already added this (and other) ApacheDS artifacts, so
> they are available as OSGi bundles.
I have no problem moving DnNode class to core-API, except that it's 
probably not the right timing to do so. What bugs me is that this class 
was added in shared way before the core-api module was created. May be 
we forgot to move it back then. I do feel we may use it for other 
purposes than just the server, not forcing a potential user to add 
core-api in its dependencies, but anyway, it's not a big deal.

Bottom line, I don't really care, as soon as such moves are done when 
the current work done on AP are completed, in order to ease the merge 
back to trunk (other wise it will be a nightmare), plus as soon as we 
check the impact of such moves on studio (and here, i'm not talking 
about DnNode, but about other potential changes we will have to do in 
shared before the release).

The best would be to create a JIRA suggesting moving DnNode, so that we 
can track such moves and impacts.

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com