This RFE is based on beta feedback.
Right now in JSR-047, if a logging methods is not given
an explicit source method name and class name as arguments,
then after passing its initial level based filter tests,
the Logger "eagerly" locates the caller method and class by
walking over the call stack.
However, in many cases the information may not be used, so
this is potentially a significant unnecessary cost.
Instead, the stack walk should be done lazily, when someone
first asks for the value. Thus if no one downstream from the
Logger wants to use the methodname/classname, you don't pay
the cost of the stack walk.
graham.hamilton@Eng 2001-08-01
Right now in JSR-047, if a logging methods is not given
an explicit source method name and class name as arguments,
then after passing its initial level based filter tests,
the Logger "eagerly" locates the caller method and class by
walking over the call stack.
However, in many cases the information may not be used, so
this is potentially a significant unnecessary cost.
Instead, the stack walk should be done lazily, when someone
first asks for the value. Thus if no one downstream from the
Logger wants to use the methodname/classname, you don't pay
the cost of the stack walk.
graham.hamilton@Eng 2001-08-01