http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #69 from Joern Huxhorn <joern@huxhorn.de> 2009-12-01 01:06:15 --- I'd like to encourage everybody to take a look at http://github.com/huxi/slf4j/tree/slf4j-redesign/slf4j-n-api/ Especially http://github.com/huxi/slf4j/blob/slf4j-redesign/slf4j-n-api/src/main/java/o... This patch would fix the following issues: Bug #31 Bug #70 Bug #116 Bug #125 Bug #127 Bug #133 Bug #148 * Bug #158 Further, the following Logback issues are addressed: http://jira.qos.ch/browse/LBCLASSIC-32 * ( http://jira.qos.ch/browse/LBCLASSIC-45 ) http://jira.qos.ch/browse/LBCLASSIC-76 * http://jira.qos.ch/browse/LBCLASSIC-107 http://jira.qos.ch/browse/LBCLASSIC-139 (and other MessageFormatter related threading issues) http://jira.qos.ch/browse/LBCLASSIC-163 * The issues marked with * are somehow related to the desire to be able to extend SLF5J/Logback with user-defined data. This prevented the conversion parameters to Strings during event creation, since the arguments were the sole extension point of SLF4J. The new API does now support logging of Message implementations, which can be used to support arbitrary data that is handled as a simple message by appenders unaware of specific implementations but can be handled in a special way by appenders that are aware of them (using instanceof WhateverMessage). That same feature is also enabling the use of java.util.Formatter formatted messages. As a bonus, the current slf4j-api would remain unchanged so JDK 1.4 support could be kept. The code in that branch is operational but would obviously still need testing and documentation. org.slf4j.a package isn't relevant and wouldn't be included, at least not in that JAR. The package org.slf4j.core could be put in a different JAR but this isn't really necessary, I think. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.