I'd vote for putting energy in a better classloader, one that is able to handle different versions of the same JAR file in the classpath (like DotNet... autch).
Tom
TBEE wrote:
Let me, as a log4j user, give my 2 cents. I looked at the Java 1.4 logging classes and decided they were inferior to log4j. Since log4j is an external JAR, it will not only be available in JDK1.4 but also in 1.5, ... and you can already use them in 1.3. So log4j is the way to go.
Tom
Matthias Petersen wrote:
Hi,
I saw in the 1.4 JDK that there were new classes introduced concerning logging, which seems to be a base for Log4J. When I take a look at the class hierarchy of Log4J, it is not a subclass of those JDK logging classes (I think the reason is that Log4J is older than the 1.4 JDK...).
So, what will happen with Log4J in the future ? Will it be a subclass of the Java 1.4 logging classes or will it go in a different direction ?
I think that the Log4J classes are much better than the 1.4 Java classes, but what will happen if those Java classes will become the standard for logging ? Or will Log4J be a part of the JDK somewhere in the future ?
Your answers are very important for me, because I have to decide if my company is using Log4J or if we need to enhance the 1.4 JDK logging classes.
Thanks Matthias -------------------------------------------------- Matthias Petersen ms management systems gmbh Krokamp 29 24539 Neumünster
Fon: +49. 4321. 9995-49 Fax: +49. 4321. 9995-41 E-Mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
