remm 2003/09/06 10:50:59
Modified: modules/cluster build.xml
Log:
- Modify the bundling of commons-logging to fix (hopefully) the nagging CL issues.
- The commons-logging-api JAR will now be put in the system classloader.
When using an alternate logging implmentation (ex: log4j) you should put the
wrapper implementation in the same classloader or there will likely be trouble.
- Ex: When using a Struts 1.1 webapp with log4j, there should be commons-logging.jar
(just the log4j logger is fine as well) next to it.
- Of course, overriding the log4j API in a webapp is still not possible. It wasn't
before as c-logging was treated as a special case by the classloader (like JAXP).
- This nasty case now works for me (bug 22701), as well as using log4j with
privileged webapps (with or without SSL).
Revision Changes Path
1.6 +1 -1 jakarta-tomcat-catalina/modules/cluster/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-catalina/modules/cluster/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 27 May 2003 17:00:23 -0000 1.5
+++ build.xml 6 Sep 2003 17:50:59 -0000 1.6
@@ -17,7 +17,7 @@
<!-- Construct Catalina classpath -->
<path id="cluster.classpath">
<pathelement location="${catalina.build}/server/lib/catalina.jar"/>
- <pathelement location="${catalina.build}/server/lib/commons-logging.jar"/>
+ <pathelement location="${commons-logging.jar}"/>
<pathelement location="${jmx.jar}"/>
<pathelement location="${catalina.build}/common/lib/servlet-api.jar"/>
</path>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
