Scott Deboy wrote:
.....
What would happen if we stepped back and examined what folks are really asking
for when they say they want TRACE? We also know they aren't willing to wait
for/interested in 'domains' or event attributes.
I think folks want an easy way to add new severity levels without having to
write their own log4j-related classes. Let's give THAT to them. TRACE is a
band aid that only addresses the problem for folks who want ONE new level - a
new level that's less severe than DEBUG.
What about folks who want a level between INFO & WARN or between ERROR and
FATAL, or TWO levels below DEBUG (TRACE and ULTRATRACE)? Adding support for a
'TRACE' Level and related helpers in Logger doesn't address this problem and I
think we can find a solution that supports all of these cases in common way.
......
I think you have a very good point.
I desire for a TRACE level is to, in a minimal way, get around the
manner in which log4j has tied together "kind of log/message" and "level
of that log/message". That is, "verbosity" seems to be tied together
with "type of log". In my use, I find that is not much of a problem
with ERROR and WARN but more a problem with INFO and DEBUG.
I do not so much want a TRACE level as I would an INFO and DEBUG
"verbosity" modifier.
I have previously used a C++ logging library in which
log( ERROR, 3, "my message" );
was equivalent to
error( 3, "my message" );
was equivalent (after log.setErrorLevel( 3 ); ) to
error( "my message" )
We got by fine with just error, warn, info, debug because each allowed
and optional "level" / "intensity" / "verbosity" integer modifier.
If there is not the ability to specify the intensity/verbosity, that is
kind and verbosity are intertwined, a better set is something like:
fatal, error, warn, info, verbose, debug, trace
R.Parr
Temporal Arts
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
