Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 4720 invoked from network); 16 Apr 2004 00:50:46 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Apr 2004 00:50:46 -0000 Received: (qmail 69603 invoked by uid 500); 16 Apr 2004 00:50:29 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 69516 invoked by uid 500); 16 Apr 2004 00:50:28 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 69497 invoked from network); 16 Apr 2004 00:50:28 -0000 Received: from unknown (HELO imf21aec.mail.bellsouth.net) (205.152.59.69) by daedalus.apache.org with SMTP; 16 Apr 2004 00:50:28 -0000 Received: from franklin ([65.80.197.149]) by imf21aec.mail.bellsouth.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040416005036.OOSQ1779.imf21aec.mail.bellsouth.net@franklin> for ; Thu, 15 Apr 2004 20:50:36 -0400 From: "Alex Karasulu" To: "'Apache Directory Developers List'" Subject: RE: Question on usage Date: Thu, 15 Apr 2004 20:50:32 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <31DF72A980E5D511B48C000102BD8685061DB33F@calexc01.diginsite.com> Thread-Index: AcQjNGJwZTdVRLrWQRiy5t2QEvpM9AAF+MyA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Message-Id: <20040416005036.OOSQ1779.imf21aec.mail.bellsouth.net@franklin> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Ralph, I'm not the lead on the naming JNDI provider but don't think you can use your code with it because of namespace issues. The naming code may have a provider but I think its suited to toward the java ENC namespace. If your code is written to work with an LDAP directory via the JNDI then it will not work with anything other than a JNDI LDAP provider. I would recommend using Eve's LDAP JNDI provider which basically embeds the Eve directory server's backend into your application but its still under development. Alex > -----Original Message----- > From: Ralph Goers [mailto:Ralph.Goers@digitalinsight.com] > Sent: Thursday, April 15, 2004 5:54 PM > To: 'Apache Directory Developers List' > Subject: Question on usage > > > > I currently have code that uses JNDI to access LDAP. I then have unit > tests > for that code. At the moment these go against a real LDAP. I would like > to > use an in-memory JNDI implementation instead to do unit testing (it really > borders on functional testing since it writes stuff and then reads it). > > Is the naming package appropriate for this? From a quick glance I'm > hoping > BaseDirContext will do the job, but I don't see a factory to set > java.naming.factory.initial to. > > Any advice would be appreciated. > > Thanks > Ralph