https://issues.apache.org/bugzilla/show_bug.cgi?id=47512
--- Comment #9 from MartÃn Schonaker <mrr...@gmail.com> 2010-01-06 06:51:50 UTC --- (In reply to comment #8) > Whilst binding objects into the global JNDI directory where the classes are > only available to the web application class loader may be possible, this is > asking from all sorts of class loading pain and memory leaks. > > On that basis I am marking this as WONTFIX. > > If you want this functionality in your environment the simplest way to achieve > it is to patch org.apache.naming.NamingContext, compile the class and then > place the class file in > CATALINA_HOME/lib/org/apache/naming/NamingContext.class > I'd also put the .java file alongside it so people can easily see what you > changed. I've found another workaround. Thanks for your time, guys. Please review these ideas when you have the time. As I said, NamingContext implementation is flawed and *that's* a cause for class loading pain. Please allow me to recommend you to check Sun's JNDI/RMI Service Provider (Object Factory implementation code available here http://www.docjar.com/html/api/com/sun/jndi/rmi/registry/RegistryContextFactory.java.html) or JBoss JNP client naming implementation as a reference. Best Regards. Martin. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
