RE: Tomcat 3.2, RMI, JNDI & Classloaders: a solution

2001-03-15 Thread Andrew Gilbert
>You can make them visible, but the class from the boot classloader or >system classloader has to know what to do -- it calls >Thread.getContextClassLoader() to get the class loader for the current >thread, and asks *that* classloader to create the new object, instead of >using the "new" operator

RE: Tomcat 3.2, RMI, JNDI & Classloaders: a solution

2001-03-15 Thread Craig R. McClanahan
On Thu, 15 Mar 2001, Andrew Gilbert wrote: > Carlos, > > Thanks. This is interesting. Can you explain what the effect of > Thread.setContextClassLoader() is? Does it make classes from the > WEB-INF/lib and WEB-INF/classes area avaiable to classes loaded by > the boot class or system class loa

RE: Tomcat 3.2, RMI, JNDI & Classloaders: a solution

2001-03-15 Thread Andrew Gilbert
Carlos, Thanks. This is interesting. Can you explain what the effect of Thread.setContextClassLoader() is? Does it make classes from the WEB-INF/lib and WEB-INF/classes area avaiable to classes loaded by the boot class or system class loader? Andrew -Original Message- From: Carlos Pita