Berin Loritsch wrote:
Niklas Therning wrote:
Carsten Ziegeler wrote:
Yes, please :) I would suggest log4j as commons-logging has problems
with classloading (afair) and noone is using jdk14 logging.
Nowadays there's also slf4j (www.slf4j.org). Like commons-logging it's
a facade for other logging frameworks but it doesn't suffer from the
classloading problems of commons-logging. It's used by the Apache
directory project. I think it's being developed by the guy behind log4j.
Given the Avalon framework interfaces, we already have a log abstraction
using the LogEnabled and Logger interfaces. Proper wrappers are also
provided for Log4J and have been for years. There's no value add in
introducing YALF (Yet Another Logging Facade).
In the future when your components have no ties to Avalon, just use
Log4J directly.
Yes, I wouldn't have a problem with that. Just wanted to mention slf4j
for those who hadn't heard of it before. But it seem like you guys
already been discussing these thing in the past (I wouldn't know since
I'm quite new to the list).
/Niklas
- Re: Logkit (I know, again) was [RT] Using Spring instead ... Niklas Therning
-
