Hi,
one major advantage(to me, i acknowledge ;-) ) of the java.util.logging
package over log4j and other logging libraries is its security.
it uses the underlying java security infrastructure by securing logs with
loggingpermission use.
have you any plan to use loggingpermission?
it can be used very easily to control any logging configuration change.
other use case can stands on loggingpermission to prevent some programers to
use loggers of some packages for example.
if you are interested to implemented this feature, i can help you to
understand java security internals if needed.
cheers,
Charles GAY
www.jguard.net
--
View this message in context: http://www.nabble.com/loggingPermission-tf2731649.html#a7619191
Sent from the Logback User mailing list archive at Nabble.com.
November 30th, 2006 - Release of version 0.6
Version 0.6 of logback has been released.
Logback classic now supports automatic configuration, allowing test and production
environment configuration. TurboFilters make their first appearance in a logback
release. They provide ultra-fast filtering possibilities. The logging context now
supports listeners which will be contacted each time the context is reset or started.
SMTPAppender allows for much more flexible configuration than before.
In logback access, new Appenders are available, namely SocketAppender and DBAppender.
Logback access now supports filtering and event evaluations. A CountingFilter has
been added. It provides statistical views of server access, reachable via JMX.
The documentation has also been improved. A complete new chapter has been added about
Appenders, the short introduction to logback classic has been updated and a new
module, containing many configuration examples has been added.
Logback now uses continous integration in its development.
Tests have been improved, many new have been added. This release also provides some
bug fixes.
--
Sébastien Pennec
sebastien(a)qos.ch
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch/
Hello,
I'm new to LogBack and I was wondering why log methods do not have a varargs
version, so that one does not need to construct an array of parameter
objects.
Thanks,
Zohar.
In version 0.5 of logback the logback-access jar file does not contain the
slf4j API, unlike the same jar file of version 0.3. What jar file should I
add in order to be able to migrate to the new version?
--
YF
