Hi, This is in reference to the email below. Im new to the log4j concept and seek some help. Im not able to understand why the subclassing of Logger class is discouraged? Are there any performance related issues?? I would appreciate if someone could help me out with this issue as soon as possible.
Thanks and regards, Manoj Rathod -----Original Message----- From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 09, 2002 5:31 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: log4j 1.2 now available Greetings to all, About a year after the release of log4j 1.1.3, log4j 1.2 (final) is available at last. Compared to 1.2rc1 release, 1.2 final consists of only bug fixes and a few cosmetic changes. In addition to many performance improvements, bug fixes, and other small enhancements, log4j 1.2 adds JMX support, Mapped Diagnostic Contexts, JDBC logging, graphical log viewer (chainsaw), and buffered IO capability. One important change is the replacement of the Category class with Logger class and the Priority class with the Level class in order to facilitate migration from the JDK 1.4 logging API to log4j. Version 1.2 is the 22nd major public release of log4j. All changes except the removal of deprecated methods are backward compatible such that log4j 1.2 can be considered a drop in replacement for log4j 1.1.3. The only exception is the renaming of the CategoryFactory class to LoggerFactory class such that subclasses of Category class to be modified and recompiled. By the way, we strongly discourage casual users from subclassing the Category or Logger classes. See the docs/HISTORY file for a detailed list of changes. -- Ceki Gülcü -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
