|File Search||Catalog||Content Search|
It is possible to enable logging at runtime without modifying the application binary. The log4j package is designed so that log statements can remain in shipped code without incurring a high performance cost.
One of the distinctive features of log4j is the notion of hierarchical loggers. Using loggers it is possible to selectively control which log statements are output at arbitrary granularity.
Log4j can output to: a file, a rolling file, a database with a JDBC driver, many ouput asynchronously, a JMS Topic, a swing based logging console, the NT event log, /dev/null, a SMTP server (using javamail), a socket server, syslog, telnet daemon and stdout.
The format of the output can be defined using one of the various layout (or user defined layout) like: simple text, html, date, pattern defined and XML.
This package contains the natively compiled code for use by gij.
jakarta-log4j (1.2.15-4) unstable; urgency=low * liblog4j-java: Depend on default-jre-headless as the preferred runtime, keep the existing alternatives for now. -- Matthias Klose <firstname.lastname@example.org> Mon, 04 Aug 2008 23:55:26 +0200 jakarta-log4j (1.2.15-3) unstable; urgency=medium * debian/control: + Use default-java-jdk in place of java-gcj-compat-dev. (Closes: #477866) + S more»
This package was debianized by Benoit Joly <email@example.com> on Sat Apr 12 2003 18:32:20 -0400. It was downloaded from: http://jakarta.apache.org/log4j/docs/download.html Upstream Authors: Copyright (C) 1999-2007, The Apache Software Foundation Contributors: Mathias Bogaert James P. Cakalic Paul Glezen Ceki Gülcü Anders Kristensen Jim Moore more»