I'm not convinced that slf4j is any better than the more widely used
commons-logging.
Market share or product market penetration often do not directly reflect
the quality of one product compared to another one. It merely reflect
the power of one supplier to impose its products over the other ones; It
is not unexpected to see commons-logging still having more market
penetration than SLF4J since commons-logging was there earlier and since
many ASF framework largely use it.
Taking your words literally, then no-one should bother to use iBatis
since the market ORM/persistance is largely dominated by Hibernate which
have a huge advance in market share over any other ORM/persistance
frameworks. The same goes true for things like Firefox against IE, Linux
against Window, even Windows7 against WindowsXP.
If we want logging autonomy I'd rather go with what we did in the last
version and simply implement an internal commons-logging-ish solution.
I'm completely shocked that you did this. What was so wrong with SLF4J
or commons-logging that you decided to hack your own logging abstraction
layer? Standing by your own statement, how can you be convinced that
your hack is any better than the more widely used SLF4J or commons-logging?
ZC
Brandon Goodin wrote:
I'm not convinced that slf4j is any better than the more widely used
commons-logging. I know there are those who believe passionately on
both sides of this discussion and I don't mean to berate anyone. If we
want logging autonomy I'd rather go with what we did in the last
version and simply implement an internal commons-logging-ish solution.
Brandon
On Tue, Aug 18, 2009 at 11:22 AM, Cyril Pfaff <cyril.pf...@gmail.com
<mailto:cyril.pf...@gmail.com>> wrote:
Hi,
Thanks for this amazing product.
Currently, iBATIS3 currently depends on log4j. Even if I like
log4j, It would be interesting to look at SLF4J
(http://www.slf4j.org/) as it may offers more flexibility
(Basically due to the fact that it's an abstraction layer for
various logging frameworks.)
I did not find anything interesting in the mail archive regarding
this subject:
So ... what about slf4j ? Has this option already been discussed
and rejected internally, or is it possible to use this logging
facility instead of log4j in the next releases of iBATIS3 ??
Thanks again for your time.
Regards.
c.
