Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 38302 invoked from network); 4 Jan 2008 14:36:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jan 2008 14:36:01 -0000 Received: (qmail 25205 invoked by uid 500); 4 Jan 2008 14:35:48 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 25160 invoked by uid 500); 4 Jan 2008 14:35:48 -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 25139 invoked by uid 99); 4 Jan 2008 14:35:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2008 06:35:48 -0800 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 (nike.apache.org: domain of akarasulu@gmail.com designates 209.85.146.182 as permitted sender) Received: from [209.85.146.182] (HELO wa-out-1112.google.com) (209.85.146.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2008 14:35:37 +0000 Received: by wa-out-1112.google.com with SMTP id m38so10778459waf.5 for ; Fri, 04 Jan 2008 06:35:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=KcDH737NLZpJq/WVxdi04ZCl/EOEmUriMhnl49skIcw=; b=NUaMU75pG8zHj+2iHCS7dazUxhanp2F6mRi6iYppCU7sCOKhnDtqqVCaxLpNCJse0x9AyS42P2XstIetam2PZuAsgDgAKm8nTQ29csfsFca7JL1UwB6Vc91im+S6O9JyDphus3yf8HLqxvcX9zaYX8saf35RuddF8LurhCmErvM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=cytF4iXV6cxLEyhcQxWRidBgM1iwxL+IM6P/XMA2qGzH6nCu1udcTy1fEoULlM5PHCZnwgLypXBR9f6KoSDz24RB7ydQs9SO5elVJnBDTFioptXMKQPFhaAFvx9mCRvoz9pOZowts6Q+t1S2njPwTcDgU6u+KjtLbDwIiJjiIEs= Received: by 10.114.184.7 with SMTP id h7mr17211036waf.28.1199457328106; Fri, 04 Jan 2008 06:35:28 -0800 (PST) Received: by 10.115.76.20 with HTTP; Fri, 4 Jan 2008 06:35:28 -0800 (PST) Message-ID: Date: Fri, 4 Jan 2008 09:35:28 -0500 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: DS 1.5.2, JNDI & CoreContextFactory In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_19152_22816203.1199457328099" References: X-Google-Sender-Auth: c6464f014900eefc X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_19152_22816203.1199457328099 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Simon, We intend to remove all of JNDI so these capabilities will no longer be available. You might have guessed that from the [BigBang] discussions. There will eventually be a JNDI wrapper but it will not be like before. Thoughts? Alex On Jan 4, 2008 5:32 AM, wrote: > Prior to 1.5.2 you could connect to an embedded directory instance using > an environment hashtable of String values: > > ContextFactory:*org.apache.directory.server.jndi.ServerContextFactory > *ContextProviderURL: > ContextSecurityAuthentication:*simple* > ContextSecurityCredentials:*secret* > ContextSecurityPrincipal:*uid=admin,ou=system* > > This hashtable could be bound into JNDI and used by other services. > > As of 1.5.2 we need: > > ContextFactory:*org.apache.directory.server.core.jndi.CoreContextFactory* > ContextProviderURL: > ContextSecurityAuthentication:*simple* > ContextSecurityCredentials:*secret* > ContextSecurityPrincipal:*uid=admin,ou=system* > org.apache.directory.server.core.DirectoryService:* Instance>* > > First Point: We can no longer bind this into JNDI as > DefaultDirectoryService is not serializable. > > Second Point: We can no longer specify these attributes via a > jndi.properties file (see javadoc on InitialContext) > > If the intention was to allow the selection of a specific instance of an > embedded DirectoryService you could use the instanceId... maybe passed via > the ContextProviderURL attribute? > > ContextProviderURL: *java://MyDirectory* > > CoreContextFactory would then have to find the service instance using the > given name (or null if instanceId was not given) > > The requirements of the 1.5.2 CoreContextFactory seems to break the JNDI > API usage model and has broken our implementation. > > Any and all comment appreciated. :-) > > - SimonT > ------=_Part_19152_22816203.1199457328099 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Simon,

We intend to remove all of JNDI so these capabilities will no longer be available.  You might have guessed that from the [BigBang] discussions.  There will eventually be a JNDI wrapper but it will not be like before.

Thoughts?

Alex

On Jan 4, 2008 5:32 AM, <Simon.Temple@saaconsultants.com> wrote:
Prior to 1.5.2 you could connect to an embedded directory instance using an environment hashtable of String values:
 
ContextFactory:org.apache.directory.server.jndi.ServerContextFactory
ContextProviderURL:
ContextSecurityAuthentication:simple
ContextSecurityCredentials:secret
ContextSecurityPrincipal:uid=admin,ou=system
 
This hashtable could be bound into JNDI and used by other services.
 
As of 1.5.2 we need:
 
ContextFactory:org.apache.directory.server.core.jndi.CoreContextFactory
ContextProviderURL:
ContextSecurityAuthentication:simple
ContextSecurityCredentials:secret
ContextSecurityPrincipal:uid=admin,ou=system
org.apache.directory.server.core.DirectoryService:<DirectoryService Instance>
 
First Point:      We can no longer bind this into JNDI as DefaultDirectoryService is not serializable.
 
Second Point:  We can no longer specify these attributes via a jndi.properties file (see javadoc on InitialContext)
 
If the intention was to allow the selection of a specific instance of an embedded DirectoryService you could use the instanceId... maybe passed via the ContextProviderURL attribute?
 
    ContextProviderURL: java://MyDirectory
 
CoreContextFactory would then have to find the service instance using the given name (or null if instanceId was not given)
 
The requirements of the 1.5.2 CoreContextFactory seems to break the JNDI API usage model and has broken our implementation.
 
Any and all comment appreciated.  :-)
 
- SimonT

------=_Part_19152_22816203.1199457328099--