I had codded a client before the configuration system changed.
When I updated to the last apacheds, I changed nothing in my client code
and it worked perfectly using JNDI properties system.
This is the server wich work with this new congiguration system. And I
had just to change its property file by a xml configuration file.
Hope this help,
Tony Blanchard
Nick Faiz a écrit :
Hi,
It appears that *every* client connection via JNDI must have a
org.apache.apache.ldap.server.configuration.Configuration object
stored within it. In other words, whenever I want to bind against an
Apache DS LDAP instance:
e.g.
ldapContext = new InitialLdapContext( env, null );
I will have to ensure that my env variable contains a config. object!
I understand that the configuration object can be gained from the
Spring context but how will a remote client access it? Surely the
client shouldn't have to know a thing about the configuration of the
server, so long as it fulfills the general contract of behaving as an
LDAP client? :) If I've misunderstood something, please let me know.
Cheers,
Nick
P.S. From org.apache.ldap.server.jndi.AbstractContextFactory:
public final synchronized Context getInitialContext( Hashtable env )
throws NamingException
{
Configuration cfg = Configuration.toConfiguration( env );
//...
From org.apache.ldap.server.configuration.Configuration:
public static Configuration toConfiguration( Hashtable
jndiEnvironment )
{
Object value = jndiEnvironment.get( JNDI_KEY );
