|
From: Stephane B. <sba...@ap...> - 2004-07-08 17:36:26
|
Rod Johnson wrote: > I'm getting over 30 failures when running tests in Eclipse. Some are > JDO-related, and may be genuine failures. The others are JNDI related and > look like some static side-effect is sitting around in the > NamingContextBuilder. (Eclipse keeps the same JVM up.) The problem with the current implementation of the context builder is that as that it is a singleton in the jndi factory and that it has the highest configuration priority. If you want to use this naive but useful jndi implementation for your tests and that at the same time you want to use ldap... basically you are cooked as the sent context is not a dircontext. I needed to use a jndi provider for a command line application that was also deployed in a servlet container which was making use of jndi for configuration. I noticed that because the application was using ldap heavily and it was complaining about the context. Honestly I did not investigate too much as it was a last minute fix for a customer, and I solved the problem by using catalina-naming provider (a 10 line change with my spring configuration) Cheers, Stephane |