| Emmanuel Lecharny 2007-10-18, 7:11 am |
| What I can see is that when initializing the server (LdapServer),
looking at the server.xml file :
<ldapServer id=3D"ldapsServer"
enabled=3D"false"
ipPort=3D"60636"
enableLdaps=3D"true">
<directoryService>#directoryService</directoryService>
<socketAcceptor>#socketAcceptor</socketAcceptor>
</ldapServer>
the constructor is called first. As the reference to #directoryService
is not set yet, and as it is needed into the constructor, it resolves
to null.
Is there a way to avoid such a problem, for instance by adding the
directory service as a parameter fo the constructor ?
Doing something like :
<ldapServer id=3D"ldapsServer"
enabled=3D"false"
ipPort=3D"60636"
enableLdaps=3D"true"
directoryService=3D"#directoryService">
<socketAcceptor>#socketAcceptor</socketAcceptor>
</ldapServer>
for instance ?
On 10/18/07, Emmanuel Lecharny <elecharny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi Alex,
>
>
> Since this commit, I'm in trouble in the ldap-protocol handler as the
> DirectoryService is null when the protocol is initialized.
>
> Any insights ?
>
--=20
Regards,
Cordialement,
Emmanuel L=E9charny
www.iktek.com
|