Some people may disagree but we have take the approach of using the
commons-logging API.
We have configured it to use log4j we appropriate.
If needed I can configure commons-logging to use JDK 1.4 logging.
You will probably find JDK 1.4 logging support in log4j via an append or
someting else in the future.

Choosing log4j is not a bad choice because it is widely used and support
options JDK 1.4 does not support now and may not support soon.

-----Original Message-----
From: Matthias Petersen [mailto:[EMAIL PROTECTED]
Sent: 24 October, 2003 16:15
To: [EMAIL PROTECTED]
Subject: Log4J vs. java.util.logging


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]

__________________________________________________________________________________________________________________________________

For information about the Standard Bank group visit our web site 
<www.standardbank.co.za>
__________________________________________________________________________________________________________________________________
        
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relating to the official business of 
Standard Bank Group Limited  is proprietary to the group. 
It is confidential, legally privileged and protected by law. 
Standard Bank does not own and endorse any other content. Views and opinions are those 
of the sender unless clearly stated as being that of the group. 
The person addressed in the e-mail is the sole authorised recipient. Please notify the 
sender immediately if it has unintentionally reached you and do not read, 
disclose or use the content in any way.
Standard Bank can not assure that the integrity of this communication has been 
maintained nor that it is free of errors, virus, interception or interference.
___________________________________________________________________________________________________________________________________

Reply via email to