Why does LogFactoryImpl in commons-logging try to load the Log implementation class first from thread classloader and then loader that loaded this class?
Is there some kind of design pattern behind this?
- Rami Ojares / Elisa Internet
----------------------------------
Man Plans, God Laughs
--European Proverb
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
