Hi, > Out of dumb interest, what's the need for JCL in Tomcat? Tomcat 5.x is > JDK 5.x only isn't it, so couldn't it be using java.util.logging?
Tomcat 5.x is JDK 1.4 and 5.0. Tomcat 5.5 looks for JDK 5.0 by default but can run on 1.4 as well. However, Tomcat 5.5 is now moving in the direction of java.util.logging for itself. One key modification to java.util.logging was needed, a LogManager that can handle per-classloader hierarchies. Remy wrote one, called JULI for now, that lives in http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/juli/src/java/or g/apache/juli/ClassLoaderLogManager.java?rev=1.9&view=log if anyone's interested. > Much of Commons needs JCL to support JDK 1.2 clients, but I'd have > thought you only have that problem in Tomcat 3 and 4 maintenance > branches? Unless the idea is just to support users who might want to > use log4j. Tomcat has many users who want to use log4j, and many users who want to use JCL and pick their underlying logging implementation at runtime. The classloader issues in JCL 1.0.x and log4j 1.2.x have been difficult to resolve. > My main complaint is that I have to have a String to create a Logger, > rather than log4j which lets me use a Class so I suspect I've not felt > the java.util.logging pain yet. Just out of curiosity, why doesn't Logger.getLogger(clazz.getName()) work for you? That's basically all the log4j factory method does when it takes a class argument, then passes through to the string version ;) Yoav --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
