078804d827
a loader, and the thread loader is set to point to a different loader that doesn't include logging ( or to a wrong value ). This happens when logging is used in certain container components, where the thread loader will point to an app that may not have/use logging. XXX What's the right order ? From a 'feature' point of view, it's better to try the thread loader first, so apps can override the default. From a security point of view, we should try the Class.forName() first, i.e. whatever is loaded in the parent loader. The current fix leaves the original order ( with thread loader used if available ). git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@138874 13f79535-47bb-0310-9956-ffa450edef68