cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Kienenberger <mkien...@gmail.com>
Subject Re: cayenne library changes log level in struts2
Date Tue, 03 Dec 2013 14:59:44 GMT
On Tue, Dec 3, 2013 at 9:43 AM, Christian Grobmeier <grobmeier@gmail.com> wrote:
> With slf4j/log4j2 you can choose your logging api at your own will too.
>
> Personally I consider Commons Logging a risk and would not add it into my
> projects today.
> Its not well maintained and future developments of the other frameworks will
> most likely not look that much into Commons Logging.
>
> But well, I am biased on that.

Yes, I'm very much aware that you are trolling and/or proselytizing as
the case may be :)   But it's a good topic to revisit occasionally.

If Cayenne were to log directly to the log4j api, that would force all
of our end-users to use log4j, at least to the point to reconfigured
log4j to log to something else.

However, as you've already pointed out, if we log against the commons
logging api, then no one even needs to use the actual commons logging
implementation.   They can use the log4j2 bridge.  They can use the
slf4j bridge.   I don't know much about logback, but my guess is that
they have a bridge as well.

Commons logging as an logging implementation may not make much sense
today, but using the commons logging api provides the maximum
flexibility as far as I can tell.

Mime
View raw message