commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From commons-...@jakarta.apache.org
Subject [Jakarta Commons Wiki] Updated: Logging/FrequentlyAskedQuestions
Date Tue, 22 Jun 2004 21:14:47 GMT
   Date: 2004-06-22T14:14:47
   Editor: RobertBurrellDonkin <rdonkin@apache.org>
   Wiki: Jakarta Commons Wiki
   Page: Logging/FrequentlyAskedQuestions
   URL: http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions

   Added FAQ about WebSphere

Change Log:

------------------------------------------------------------------------------
@@ -17,6 +17,20 @@
  * all the logging classes (both Log and the logging implementations) are deployed by the
same classloader
  * there is only 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.
 
+== How Can I Use Commons-Logging In WebSphere 5.1? ==
+
+{{{
+I'm using WebSphere 5.1. Commons-Logging doesn't seem to recognize my commons-logging.properties
file. Help!
+}}}
+
+WebSphere uses commons-logging and so it's in the root classloader. This may cause difficulties
when trying to find a configuration resource. The solution is to ensure that the right classloader
policy is set:
+
+{{{
+Set EAR classloader mode as PARENT_LAST and WAR classloader policy as Application
+}}}
+
+(With thanks to David Karlsen for this information)
+
 ----
 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message