/WEB-INF/lib/*.jar of your web application./WEB-INF/classes of your web application.System class loader classses (described above).Why does no one complain? Maybe because it is not such a popular project? The same issue happens BTW with common-daemon. If you look at the Tomcat 5.5 class loader reference, you will notice that commons-logging-api.jar was put into the bin/ directory and is available through the System classloader. However the problems caused by the Tomcat 5.5 implementation continue to affect the perception of Commons Logging. Note: the following applies to Tomcat 5.5 later versions of Tomcat store the jar in the same place but change the package name so it is only used by Tomcat itself. It is the mixture of a popular project, some unfortunate class loader decisions and the rants of people who might not understand all the implications of the web container class loaders. However, if you look closer at these rants, you will notice, that much boils down to a single phrase: "class loader problems".Ĭlass loader problems are commons-logging's fault? Hardly. Commons-logging revisited (The language of this article might reflect on the author).Think again before adopting the commons-logging API. ![]() ![]() You know whose pages these are, as examples, here are a few: ![]() If you take a look at commons logging, you will sooner or later meet the various pages that recommend not to use commons-logging.
0 Comments
Leave a Reply. |