On 5 Aug 2004, at 15:49, Shapira, Yoav wrote:
Hola,
hi
I'm forwarding this to commons-dev to include the commons-logging developers on this discussion. What do you guys think?
i'm not sure i understand what ceki's point is. i can't see that he gives any reason for pointing the finger in the way he does. maybe if ceki explained how using classloaders as keys effects log4j, i'd see a bit better...
the commons-logging classloader stuff was created IIRC by craig, remy and others. i don't feel qualified to second-guess their knowledge of servlet containers.
Is there another readily available key to use when caching LogFactory objects?
not that i know of
Or perhaps a way for commons-logging to not cache these, or maybe discard the cache when a webapp (or its classloader, more likely) is shut down?
i don't see how any of that could work. (can anyone see something that i can't?) there is a method that tomcat calls (or used to call) that does unload everything but the container or the application needs to call it explicitly.
i've wanted for a while to use a WeakHashMap so that old classloaders who be garbage collected but don't see that there's an easy way to do this without breaking compatibility. i have some ideas about how to make it easier for variant LogFactory implementations but this isn't an itch for me and i doubt very much whether i'll find the time to code anything along those lines.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
