From: Yannick M. <yan...@fa...> - 2005-02-10 23:50:07
|
Ceki Gülcü wrote: > > On Thu, 10 Feb 2005 14:30:19 +0000, Yannick Menager wrote: > > > No, actually that's the whole reason behind using the ClassLoader > > Factory cache, each classloader has it's own private log > > implementation. So two webapps can each have it's own private version > > of log4j, for example. In that aspect the JCL discovery system is > > quite good, the problem comes from the fact that they use the > > Hashtable to map ClassLoader to Factory, which is the root of all the > > JCL evils. However that is easily solved by using a WeakHashMap > > instead ( losing 1.1 compatibility by doing that ). > > Hello Yannick, > > Problems of Type-III, that is holding references to class loader > instances, is just the tip of the iceberg. JCL's problems of Type-I > and Type-II are more subtle, harder to spot and tend to be diffused > throughout the code. Unless you have a JVM embedded in your brain, you > can be staring at the bug for an hour and still not see that it is > there. Hmm... interesting, i thought that was the only problem... Can you point me to some more details on those Type-II problems |