[slf4j-dev] [Bug 13] JDK14LoggerAdapter does not preserve source class name

[bugzilla-daemon at gil.qos.ch]

http://bugzilla.slf4j.org/show_bug.cgi?id=13





------- Additional Comments From sbate at smart-trade.net  2006-04-20 12:35 -------
(In reply to comment #16) 
> The solution currently in SLF4J can be found in JCL and other places. As far
> as I am aware, the question of performance is rarely if ever raised. In a
> perfect world, JDK14 logging would have hooks for extensions.

Hi Ceki,

It probably isn't a significant issue for a large majority of applications.
Given that my users are more likely to be sensitive to performance issues
(financial trading domain) and to actually run profilers to identify performance
issues, I'll need to warn them clearly about this issue. I already provide
optional JARs for using Log4J instead of the JDK 1.4 logging but I'm trying to
minimize the default external JAR dependencies. I realize I also have the option
of writing my own optimized JDK 1.4 logging adapter, if it's necessary. ;-)
Since the original decision about this issue was based partially on lack of any
feedback indicating it might be a problem, I wanted to go on record that I have
concerns about it -- for myself and the users of my library. My concern may be
relatively rare, but I doubt that I am alone.



-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.