You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by "Pill, Juergen" <Ju...@softwareag.com> on 2001/03/16 14:06:23 UTC

Log4J Logger

Hello,

we are planing to map the channel specification used in the Slide Logger
interface to the Log4J category. Additionally we are planing to extent the
logger interface with an additional set of methods (similar to log4J):

	isDebugEnabled()
	isInfoEnabled()
	isEnabled(String channel, int level)

In case of SimpleLogger the implementation would be always return true
(taking the actual level set into account).
In case of Log4JLogger the call would be delegated to the Log4J system,
taking the level and the channel/category into account.

Currently the channel specifiaction is not used in Slide (to my knowledge),
so this change would not effect the current behaviour.
In the future following method calls could be used and individually switched
on/off with the Log4JLogger. The simpleLogger would not distinguish between
channels (like todays implementation)

	Domain.log("some trace", "org.apache...SomeCategoryName" ,
someLevel);

Do you want me to perform these changes beginning next week?

Best regards

Juergen Pill

Re: Log4J Logger

Posted by Remy Maucherat <re...@apache.org>.
> Hello,
>
> we are planing to map the channel specification used in the Slide Logger
> interface to the Log4J category. Additionally we are planing to extent the
> logger interface with an additional set of methods (similar to log4J):
>
> isDebugEnabled()
> isInfoEnabled()
> isEnabled(String channel, int level)
>
> In case of SimpleLogger the implementation would be always return true
> (taking the actual level set into account).
> In case of Log4JLogger the call would be delegated to the Log4J system,
> taking the level and the channel/category into account.

+1

> Currently the channel specifiaction is not used in Slide (to my
knowledge),
> so this change would not effect the current behaviour.
> In the future following method calls could be used and individually
switched
> on/off with the Log4JLogger. The simpleLogger would not distinguish
between
> channels (like todays implementation)
>
> Domain.log("some trace", "org.apache...SomeCategoryName" ,
> someLevel);
>
> Do you want me to perform these changes beginning next week?

Yes, that's a good idea.

I added the possibility to associate a different logger to each namespace
some time ago. Of course, at the moment, everything in Slide is directly
logging to the Domain's logger.

Also, I think it would be nice to have the different components log to a
different channel (security, transaction manager, etc). Perhaps that's what
you were planning.

In the configuration, the logger should be moved and become a full fledged
element (instead of being an attribute), so that parameters can be specified
(that would be useful for log4j, to specify the appender).

Remy