Dennis Lundberg wrote:
Hi
Diagnostics, that was introduced in Commons Logging 1.1, is a great way
to troubleshoot classloading issues:
http://jakarta.apache.org/commons/logging/troubleshooting.html#Using_JCL_Diagnostics
I'm not really in doubt what's going on, so I don't think diagnostics
would help me.
Essentially I would like LogFactory to use it's own classloader instead
of the context classloader.
This is because I'm trying to load some classes by one (parent)
classloader, and invoking methods afterwards that are supposed to use
another (child) classloader.
Thanks,
-dennis
---------------------------------------------------------------------------
The information in this email is confidential and may be legally protected.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
