I just wanted to recommend switching to /SLF4J/ after looking at the
sources (for the first time :) ). It is sometimes hard to live with
/commons-logging/...
(Although I haven't used it before "seriously", the /logback /framework
seems to be a very good and well documented logger implementation. It
supports /SLF4J /natively resulting in better logging performance for
example.)
Regards:
Norbi
Massimo Lusetti írta:
On 7/1/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I've been strongly thinking about this again; probably the last chance
to do so while T5 is still in alpha.
It really comes down to:
- Leave status quo / commons-logging
- Adopt SL4J
- Adopt JDK logging
The big area this affects is the way a Log can be injected into a
service; the interface injected, etc., may change.
For me the SL4J and JDK logging are both fine, i've gone through a
test with SL4J and the current trunk and it has been easy to switch to
it, some test (one in ioc) fails but i think it's workable.
Plus using jcl12-over...jar from SL4J let you switch without changing
a line of java code which seems and easy first step to give it a try.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
