[slf4j-dev] [Bug 80] JDK14LoggerAdapter should lazily create stack traces

[bugzilla-daemon at pixie.qos.ch]

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


listid at qos.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Comment #1 from listid at qos.ch  2008-05-28 22:10 -------
Hello Matthew,

Indeed, by subclassing LogRecord it would be possible to override the
getSourceClassName and getSourceMethodName methods to trigger lazy
initialization of the relevant fields. 

The current eager initialization works but wastes CPU time. However,
subclassing the LogRecord class may conflict with other implementations of JUL.
This is not such a far-fetched scenario as Weblogic application server has its
own enhanced implementation of JUL. Thus, I am tempted to leave things as they
are: somewhat slow but not broken either. It can also be argued, albeit lamely,
that JCL's approach is not any faster.


-- 
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.