Thanks Christoph, like i mentioned before we don't want to carry more
bridges into logging. I'm not against moving towards log4j2 and i already
changed my entire code base to use log4j2 as a part of struts2 upgrade but
the problem here is application server support, we are using latest version
Wild
2016-07-19 10:55 GMT+02:00 Sreekanth S. Nair :
> Hi Christoph,
>Thanks for your detailed explanation, even though
> its a huge change for application to move from both slf4j and log4j1 to
> Log4j2, lets assume we moved all to Log4j2 but if the underlying
> application server
> From: "Sreekanth S. Nair"
> To: Struts Users Mailing List ,
> Date: 19.07.2016 10:55
> Subject: Re: [ANN] Apache Struts 2.3.30 GA
>
> Hi Christoph,
>Thanks for your detailed explanation, even though
> its a huge change for application to move from both slf4j and log4j1
Hi Christoph,
Thanks for your detailed explanation, even though
its a huge change for application to move from both slf4j and log4j1 to
Log4j2, lets assume we moved all to Log4j2 but if the underlying
application server eg: Jboss or wildfly have its own wrapper implementation
> I'm not sure about bridging log4j1 to log4j2 gives us any benefit from
> enduser point of view, and most the people were using slf4j and log4j 1
for
> sure, with the addition of log4j2 the chain is getting complex for a
simple
> logging.
>
>
In our apps we have been using slf4j and log4j1
5 matches
Mail list logo
