[
https://issues.apache.org/jira/browse/OWB-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-687:
------------------------------
Description:
There is a very old discussion about static loggers vs non-static loggers. More
about it here:
http://wiki.apache.org/commons/Logging/StaticLog
To sum it up quickly: Some logging frameworks have problems to distinguish
between logLevels in different ClassLoaders. They move the responsibilities to
the 'user' of the logger. For those frameworks you need to create an own Logger
instance for each and every invocation. That sucks big times and is a severe
performance impact.
My stance for it is that Logging for shared components is usually configured on
a general basis. If an application server likes to provide TCCL-Logging, well
then they should take a Logging Backend which provides this! I don't see a
reason for trashing the performance for 98% of all use cases only for just a
very few situations. At least if there are other options as well for those.
was:
There is a very old discussion about static loggers vs non-static loggers. More
about it here:
http://wiki.apache.org/commons/Logging/StaticLog
To sum it up quickly: Some logging frameworks have problems to distinguish
between logLevels in different ClassLoaders. They move the responsibilities to
the 'user' of the logger. For those frameworks you need to create an own Logger
instance for each and every invocation. That sucks big times and is a severe
performance impact.
My stance for it is that Logging for shared components is usually configured on
a general basis. If an application server likes to provide TCCL-Logging, well
then they should take a Logging Backend which provides this! I don't see a
reason for trashing the performance for 98% of all use cases just a very few
situations where there are other options as well.
> clean up non-static loggers
> ---------------------------
>
> Key: OWB-687
> URL: https://issues.apache.org/jira/browse/OWB-687
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.4
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.1.5
>
>
> There is a very old discussion about static loggers vs non-static loggers.
> More about it here:
> http://wiki.apache.org/commons/Logging/StaticLog
> To sum it up quickly: Some logging frameworks have problems to distinguish
> between logLevels in different ClassLoaders. They move the responsibilities
> to the 'user' of the logger. For those frameworks you need to create an own
> Logger instance for each and every invocation. That sucks big times and is a
> severe performance impact.
> My stance for it is that Logging for shared components is usually configured
> on a general basis. If an application server likes to provide TCCL-Logging,
> well then they should take a Logging Backend which provides this! I don't see
> a reason for trashing the performance for 98% of all use cases only for just
> a very few situations. At least if there are other options as well for those.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
