[logback-announce] 10 reasons to switch to logback

Ceki Gülcü listid at qos.ch
Tue Oct 24 22:18:58 CEST 2006


As you may have already heard, I have been working on a new project
called logback, intended as a worthy successor of log4j.

On the 5th of December, I'll will be presenting (in French) the top 10
reasons for migrating your projects to logback. Issues such as
migration strategy, new APIs, SLF4J and Joran will be
discussed. Emphasis will be given to practical aspects and a live demo
rather than relatively theoretical considerations.

This free-entry event is organized by Hortis SA. Information regarding
the venue can be found at the following pages:


For those who may not be able to attend this presentation, here is a
brief summary:

- Logback is an improved version of log4j
- Given that logback is built on top of SLF4J, you can switch to a
   another logging system at will.
- The new Joran configuration API sits at the core of logback. Joran
   offers a generic, powerful and flexible configuration API.
- The Status API for Accrued resilience. Logback's status API enables
   internal error reporting in a simple yet powerful way without adding
- Documentation: already good and getting better by the day.
- Filtering API. If you can imagine it, logback can filter it.
- Marker objects to color log statements for highly-specialized processing.
- Access module: easy integration with access logs generated by Tomcat
   or Jetty
- JMX: You can configure logback at runtime using Mbeans.
- TDD: logback has been developed test first and it is available for
   use, today.

The contents of the powerpoint presentation are available at:


I hope you can make it. I would be delighted to meet you in person.

Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.

More information about the announce mailing list