I have used SLF4J for some time now in a number of projects and did
not have any (serious) problem yet.
The biggest problem was that some classes where not serializable. So
when used in web apps that store objects with loggers in session or
client this was an issue of course. But this was fixed in
Hello everyone, we have been using commons-logging the past years.
I am not sure if it is a good idea,
first of all java has a decent logging api, which would allow us to
eliminate the logging dependency.
Secondly,I have not looked into the code yet, but there are a load
of references that
Hello Werner,
I would like to replace commons-logging with slf4j:-)
Regards
Bernd
Werner Punz schrieb:
Hello everyone, we have been using commons-logging the past years.
I am not sure if it is a good idea,
first of all java has a decent logging api, which would allow us to
eliminate the
Werner Punz schrieb:
Hello everyone, we have been using commons-logging the past years.
I am not sure if it is a good idea,
first of all java has a decent logging api, which would allow us to
eliminate the logging dependency.
Using a logging API built into the JDK does feel tempting.
However
Ok I just saw that the slf4j people provide a thin api layer
which replaces the commons logging if needed.
Then probably replacing commons logging is a non issue.
I just was raising this issue again, due to the problems i read
about log4j especially in combination with was and other big irons
