Hi John!
I'm using IBM's Logging Toolkit for Java aka JLog
(http://alphaworks.ibm.com).
I just replaced turbine's org.apache.util.Log class to use JLog in turbine
and I am very happy with this solution. I made only minimal changes but it
had great effects:
JLog makes it possible to log to different output-handler's and
filter/format each handler in a different way.
Each message or trace/debug entry that is logged may be marked with a
seperate level information (info, warning, error, fatal, debug, method
entry/exit....).
Each JLog component may run synchronously or asynchronously.
The most important advantage in my opinion is the possibility to use a
LogManager. It configures the logging environment with a set of properties
files.
The developer only needs to get a logging object from the LogManager and to
send his log entries. Output-handlers, filters and formatters are configured
by the admin via the properties.
Unfortunately JLog's sources are not free. But I'm not in this licensing
stuff. Simply have a look at the homepage above.
> I havent decided between log4j and avalon's log package. Although they
both
> seem pretty similar, log4j seems to have a little more documentation. If
> anyone wants to argue for one over the other pelase do so now.
I had a look at both packages:
The avalon package seems to be in a very early development state. The idea
looks good, but there is lot of work to be done before it may be used in a
real environment.
log4j is ready-to-use but there are too many configuration aspects that need
to be coded in the system. Thus log4j is not very flexible.
If the licensing makes it impossible to use JLog I would be in favour of
avalon's logging interfaces. Every developer may modify it to his own
preferences.
Any comments?
David
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
