logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 43204] Contribution Java 5+ Improvements: String formatter, stack trace inspection
Date Thu, 07 Aug 2008 21:39:42 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=43204


Curt Arnold <carnold@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|                            |DUPLICATE




--- Comment #8 from Curt Arnold <carnold@apache.org>  2008-08-07 14:39:41 PST ---
LogMF (or LogSF for the special case of migrating log4j 1.3 code) is a much
better recommendation that slf4j if all the user is trying to do is to be able
use parameterized messages.  It supports the syntax and all the capabilities of
java.util.MessageFormatter.  The incompatible specification syntax used by
log4j 1.3 and SLF4J was rationalized by a supposed performance advantage over
java.util.MessageFormatter, however it was fairly trivial to accelerate the
performance for the trivial cases so that LogMF is as fast or faster for the
subset of cases supported by SLF4J formatting.

As LogMF and LogSF seem to address all the concerns of the original bug.  I'm
going to mark this as a duplicate of 42783 which is the closest to the bug
report backing the original development of LogMF.

*** This bug has been marked as a duplicate of bug 42783 ***


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message