At 17:17 18.01.2002 -0700, Herman, Dave wrote: >> This FAQ item is actually misleading. >> >> Log4j does not attempt to do any class loading itself. I >> repeat, log4j does not >> do classloading. > >Actually, it's when the PropertyConfigurator loads an appender class that it >calls Thread.currentThread().getContextClassLoader().loadClass(name). The >behavior in 1.1.3 was simply to call Class.forName(name). This is where the >problem is: Ant doesn't set the context class loader, so some classes are >being loaded by the Ant class loader and others are being loaded by the >context class loader, which is the default JRE loader.
My mistake. I should not write emails past midnight. What I meant was log4j does not have its own classloader. I'll change the PropertyConfigurator. Thanks for the valuable information. Ceki. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
