commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Jakarta-commons Wiki] Update of "Logging/FrequentlyAskedQuestions" by SimonKitching
Date Tue, 14 Mar 2006 00:04:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.

The following page has been changed by SimonKitching:

The comment on the change is:
Add known issue re Tomcat Jspc and Ant

   * All the logging classes (both Log and the logging implementations) are deployed by the
same classloader. In other words, place commons-logging.jar and the logging library jar in
the same directory.
   * There is only one copy of the classes to be found within the classloader hierarchy. In
application container environments this means ensuring that if the classes are found in a
parent classloader, they are not also present in the leaf classloader associated with the
application. So, if the jar is deployed within the root classloader of the container then
it should be removed from the application's library.
+ === Known causes of "does not implement Log" ===
+ ==== Running JspC from Ant ====
+ The Tomcat JspC tool compiles JSP pages into bytecode. It had a bug in versions prior to
5.5.5 or 5.0.30. where
+ it set the context classloader to a non-standard value, then failed to reset it to the original
+ on exit. When run "in-process" as an ant task this would cause commons-logging to try to
load logging libraries
+ from an invalid classloader. This bug has been fixed in the 5.5.5 and 5.0.30 releases of
  == How Can I Use Commons-Logging In WebSphere 5.1? ==

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message