Thanks Chris,
I have tried this before - with little success. The code does not through
any exception now - but the DirContext object (ctx) is null and by that
unusable:
DirContext ctx = (DirContext)
newCtx.lookup("java:comp/env/blah");
if (ctx != null){
System.out.println ("True");
} else {
System.out.println ("False");
}
I have also tried to list the bindings on comp/env - but there I also get a
NullPointerException:
NamingEnumeration ne = newCtx.listBindings("java:comp/env");
while(ne.hasMore()) {
Binding b = (Binding) ne.next();
System.out.println(b.getName() + " " + b.getObject());
}
Any good suggestion to what is going on? I think that I read that you could
enable debugging on a resource definition - but I seem not to find it any
again.
NOTE: If I use the more regular approach to connect to the ldap server in
another servlet - then I have no trouble at all (just to verify the
credentials):
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL,
"ldap://192.168.7.1:389/dc=blah,dc=com";);
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, "cn=blah");
env.put(Context.SECURITY_CREDENTIALS, "blahblah");
DirContext ctx = null;
try {
ctx = new InitialDirContext(env);
} catch (NamingException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
Thanks
/Poul
billybob79 wrote:
>
>
> You should also have a matching entry in web.xml, e.g.
>
> <resource-ref>
> <res-ref-name>blah</res-ref-name>
> <res-type>com.sun.jndi.ldap.LdapCtx</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> HTH
>
> Chris
>
>
--
View this message in context:
http://old.nabble.com/JNDI%2C-resource-and-LDAP-Trouble-tp31488541p31491643.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
