Send from my mobile device
> Am 02.06.2014 um 21:51 schrieb Romain Manni-Bucau :
>
> @Thomas: never said [logging] is bad and JUL is better. Sorry if I was not
> clear. All logging facades don't handle very well EE case for several good
> or bad reasons. [logging] is as good as slf4j for it (ev
@Thomas: never said [logging] is bad and JUL is better. Sorry if I was not
clear. All logging facades don't handle very well EE case for several good
or bad reasons. [logging] is as good as slf4j for it (even better out of
the box IIRC). JUL is far to be perfect but is in the JVM (so no
dependency)
On 01.06.14 21:26, Romain Manni-Bucau wrote:
> Hi
>
> I have two main point to discuss regarding the logging:
> 1) LogHelper stuffI committed. Idea was to cache isDebugEnabled to get a if
> (boolean) complexity and not go through the logging framework which can
> imply several layers (filter, appe
On 02.06.14 17:02, Romain Manni-Bucau wrote:
> actually these logs are really debug log not intended to be activated in
> prod excepted if there is a big issue (@thomas: if you can confirm it would
> be great).
Yes, logging is for debugging purposes mostly. But if you remove them:
how would you do
actually these logs are really debug log not intended to be activated in
prod excepted if there is a big issue (@thomas: if you can confirm it would
be great).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github:
On 6/1/14, 12:26 PM, Romain Manni-Bucau wrote:
> Hi
>
> I have two main point to discuss regarding the logging:
> 1) LogHelper stuffI committed. Idea was to cache isDebugEnabled to get a if
> (boolean) complexity and not go through the logging framework which can
> imply several layers (filter, app
e a log4j 2 Jira for this? There might be one
> already though. I have seen discussions about this area on the log4j dev ML.
>
> Gary
>
> Original message From: Romain Manni-Bucau
> Date:06/02/2014 08:31 (GMT-05:00)
> To: Commons Developers List
>
Could you please create a log4j 2 Jira for this? There might be one already
though. I have seen discussions about this area on the log4j dev ML.
Gary
Original message From: Romain Manni-Bucau
Date:06/02/2014 08:31 (GMT-05:00)
To: Commons Developers List
Subject: Re: [jcs
@Gary: same with trunk. Here what I do (we can move it to another thread
since that's 100% log4j2 related): unzip
apache-tomee-1.7.0-SNAPSHOT-webprofile.zip && cd
apache-tomee-webprofile-1.7.0-SNAPSHOT/ && rm conf/logging.properties &&
echo 'openejb.log.factory=log4j'>conf/system.properties && cp
On Mon, Jun 2, 2014 at 1:20 AM, Romain Manni-Bucau
wrote:
> Well ATM log4j2 doesnt work well, didnt get time to dig into it but tested
> last week for another topic and lost all my shutdown messages (guess
> cleanup is called too early).
>
Please to check out trunk and give us some feedback! tru
Well because [logging] was longly broken in a not flat classloading
environment (didnt check last release but almost all logging facade got
this issue at a point) and because almost nothing in TomEE stacks uses it,
it is not as integrated as log4j, slf4j or JUL (which is the default). Main
issue I
Romain Manni-Bucau wrote:
> Hi
>
> I have two main point to discuss regarding the logging:
> 1) LogHelper stuffI committed. Idea was to cache isDebugEnabled to get a
> if (boolean) complexity and not go through the logging framework which can
> imply several layers (filter, appender, handler, log
Well ATM log4j2 doesnt work well, didnt get time to dig into it but tested
last week for another topic and lost all my shutdown messages (guess
cleanup is called too early).
3 would be an option if we dont rely on [logging] anymore but the impl
directly which would be a regression IMHO + either wo
There is also log4j 2.
Gary
Original message From: Romain Manni-Bucau
Date:06/01/2014 15:26 (GMT-05:00)
To: Commons Developers List
Subject: [jcs] logging
Hi
I have two main point to discuss regarding the logging:
1) LogHelper stuffI committed. Idea was to cache isDebugE
On 1 June 2014 20:26, Romain Manni-Bucau wrote:
> Hi
>
> I have two main point to discuss regarding the logging:
> 1) LogHelper stuffI committed. Idea was to cache isDebugEnabled to get a if
> (boolean) complexity and not go through the logging framework which can
> imply several layers (filter, a
15 matches
Mail list logo
