So there is no way to avoid having webapp code explicitly pointing at LDAP?
I was thinking of a workaround where I would store the LDAP connect info in the web.xml somewhere, and then read that into an object and bind it to some JNDI address, but I still don't like that solution. I'd still have to create classes to handle getting user lists from different sources, and that seems backwards to me. Isn't it the point of J2EE to abstract this stuff away from the webapps so that developers can write portable solutions with less code? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3943012#3943012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3943012 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
