LogLog is only intended to be invoked sparingly, e.g. during
configuration for debugging or when something goes wrong internally in
log4j. This means it doesn't have to be as fast as regular logging.
Anders
David Owens wrote:
>
> All,
>
> LogLog is a very cool thing, and allows a central, standard way
> to log messages from withing log4j components. However, it seems
> that it lacks the standard Category behavior which allows checking
> of logging priority. This functionality should be included so
> logging lines which do string concatination could be guarded by
> tests for that priority level. In other words:
>
> The innefecient line:
> LogLog.debug("The value was: " + myValue.toSting() + " and " +
> foo.value1);
>
> would be guarded like this:
> if(LogLog.isEnabledFor(Priority.DEBUG))
> {
> LogLog.debug("The value was: " + myValue.toSting() + " and " +
> foo.value1);
> }
>
> Any one else have thoughts on this? Perhaps LogLog should just be a
> special
> subclass of Category....
>
> I would be happy to submit some modifications like this, but I thought I
> would
> bounce it off here first.
>
> |)ave
>
> ------------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
