On 04/11/2009 12:02, Rémy-Christophe Schermesser wrote:
Hi guys,
Did you know that log4j is a dead project, and that the guy who code
it started a new java logger api& implementation (sfl4j and logback).
It seems that log4j had issues with class loaders.
Si two questions :
- Do you know those issues ?
- Do you think LSC should migrate from log4j to sfl4j& logback (sfl4j
offers a migration tool) ?
Hi Rémy-Christophe,
I was not aware that log4j was no longer developed. Thanks for the info!
Since that is the case, I think it sounds like a good idea to switch to
something actively maintained.
After looking at the SFL4J website, I noticed two things.
1) Their "parameterized messages" idea is interesting. In LSC we have
lots of DEBUG logs scattered around, that no doubt impact performance,
since we're doing toString() on all sorts of objects.
See: http://slf4j.org/faq.html#logging_performance
2) The website suggests SFL4J is only a frontend for logging, and you
need to plug in a backend. From the list they give, the only "real"
option seems to be log4j... Surely this beats the point?
See: http://slf4j.org/manual.html#swapping
Did you understand this any better? Or do you know of a better
alternative to log4j as a backend?
It would be nice to look at logging in LSC. One thing to bear in mind is
that we currently use two custom log4j layouts to output LDIF and CSV.
Do you think these could be reused, or adapted for SLF4J?
See you,
Jonathan
_______________________________________________
lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev
