Hello,
yes we are planing to have the possibility to log (via Domain) into
different channels/categories. Using SimpleLogger this is not available, but
using Log4J logger, Domain.log can be used to log to different categories.
They can be seperately switched on/off by a log4j.property file.
We are going to implement a logger, which is able to print out the request
and response data structures of each individual webdav method call, if a
certain category is switched on (therefore the isEnabled methods). We want
this logger category to print to file and pack the request and response into
XML. This XML output can be used in the future to automatically generate
test cases. We will write an XML test processor for this purpose.
Perhaps we will be able to return the XML test genarator the next few days.
(this could be something for the client too, what do you think).
More details will come soon, when the request/result logging code is
available.
best regards
Juergen Pill
-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 19, 2001 6:46 AM
To: [EMAIL PROTECTED]
Subject: Re: 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.
+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
