Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <42267004.20600@ipov.net>
Date: Wed, 02 Mar 2005 20:01:40 -0600
From: "Robert r. Sanders" <robert.sanders@ipov.net>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Apache Directory Developers List <directory-dev@incubator.apache.org>
Subject: Re: Configure (Eve) server from properties file.
References: <42252AD1.7070505@ipov.net> <42253C97.30409@bellsouth.net>
 <4226358C.50702@ipov.net> <42263F58.3070906@bozemanpass.com>
 <422645F3.4060402@ipov.net> <42264A5F.3000108@bozemanpass.com>
In-Reply-To: <42264A5F.3000108@bozemanpass.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ok,

    I haven't read the book you note, but I just looked it up and will 
think about buying it...  I have done a little JNDI in the past, but not 
a huge amount. 

    The code I am trying to write tests for is:  
http://cvs.sourceforge.net/viewcvs.py/acegisecurity/acegisecurity/sandbox/src/main/java/net/sf/acegisecurity/providers/dao/ldap/LdapPasswordAuthenticationDao.java?rev=1.4&view=log

The code's goal is to validate a username/password against an LDAP 
server (via JNDI) and retrieve a list of roles associated with the 
user.  Currently any testing is pretty dependent on a user/developer 
having an already working LDAP server; my goal is to have a bunch of 
server configurations which can be 'loaded' so I can see if my code 
returns the expected results when run against the different 
configurations - its more functional than unit testing, but if I can get 
it to work it'll be a whole lot better than the way most such code is 
tested.


David Boreham wrote:

> Robert r. Sanders wrote:
>
>> I am not trying to test the server; what I'd like to do is test some 
>> JNDI code that is designed to work against an LDAP server (OpenLDAP, 
>> ActiveDirectory, etc..) by:
>>
>> 1. Loading a server instance from the test code.
>> 2. Telling the server (if possible) to read in some schema + data.
>> 3. Configuring JNDI Client code.
>> 4. Running JNDI Client code tests.
>> 5. Shutting down server.
>>
>> Note that some server specific responses may not be testable this 
>> way; that's ok.  What I want to test is that certain client 
>> configurations return the expected results when run against known 
>> server schemas.
>
>
> Hmm...you've kind of lost me.  Perhaps you could give an example.
> I don't know what you mean by 'telling the server to read in
> some schema + data'.
>
>> Any pointers as to where to get started here?  I have been looking 
>> around for information, and pretty much everything I've found already 
>> assumes you know what it is talking about.
>
>
> Perhaps you could say where you're at in learning about this:
> Have you read Tim Howes, Mark Smith and Gordon Good's book for example ?
>
>
>

-- 
    Robert r. Sanders
    Chief Technologist
    iPOV
    (334) 821-5412
    www.ipov.net