Forget this mail. I found the solution (a setLogMethod(String logMethod)
function in the abstract base class that re-initialises the log with
<classname>:<logmethod>)

Mathias

----- Original Message -----
From: "Mathias Bogaert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 03, 2002 7:57 PM
Subject: [Xdoclet-devel] Logging


> Hi guys,
>
> I'm currently evaluating the Jakarta Commons logging package. What appears
> to be a nice interface to several logging software, it doesn't support
> getting a log by combining a class and a method. The only thing I can do
is
> manually add <classname>:<methodname> as name of the log. But this is not
> compatible with the way I want to implement logging functionality
(abstract
> LogAdapter class that implements the logging functionality).
>
> So my question is: is the method where the statement is logged important?
> You already have the class, but indeed, method information would be nice.
>
> Regards,
> Mathias
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
> _______________________________________________
> Xdoclet-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
>


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to