struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Walton <>
Subject Re: Log42j
Date Mon, 01 Jun 2015 02:48:38 GMT

> On 29 May 2015, at 5:12 pm, Christoph Nenning <> wrote:
>> Given that, perhaps direct use of SLF4J’s API would make it easier 
>> to defer the choice of Log4j 2 or, for example, LogBack to runtime? 
>> That way there would be no compile-time dependency on Log4j2-specific API.
> From the log4j2 front page:
> <>

Ah, great. I think <>
is what I was looking for, as documentation of the org.apache.logging.log4j:log4j-api artifact.

> Log4j2 wants to provide the same benefits as slf4j does. AFAIK slf4j is a 
> one man show while log4j2 has a bigger team and is backed by the ASF.

It’s a shame to end up with two separate logging facades. Despite being a one-man project,
SLF4J has a substantial number of contributors:
<> - 36, to 7 for
<>). It’s also widely
proven, and stable.

That said, the Log4j 2 to SLF4J adaptor (
<>) looks like it’ll
make simple to use Struts with an existing SLF4J environment. Then everyone can get behind
coding to a simple API and picking the best logging implementation at runtime.

Thanks for the pointers; looking forward to seeing simplification in Struts.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message