[
https://issues.apache.org/jira/browse/JCS-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Vandahl updated JCS-241:
-------------------------------
Description:
Commons JCS contains a logging wrapper in {{o.a.c.jcs3.log}}.
Using a logging wrapper causes several issues:
* Users need to set the hard to find {{jcs.logSystem}} system property to
switch between the JUL and Log4j API backend.
* Both backends lose location information, which will always point to the
wrapper class as source of all log events.
For this reason I propose to:
* Rewrite Commons JCS to use the System.Logger API directly.
* Deprecate the logging wrapper and related methods (e.g. {{JCS.setLogSystem}})
for removal in the next major version.
was:
Commons JCS contains a logging wrapper in {{o.a.c.jcs3.log}}.
Using a logging wrapper causes several issues:
* Users need to set the hard to find {{jcs.logSystem}} system property to
switch between the JUL and Log4j API backend.
* Both backends lose location information, which will always point to the
wrapper class as source of all log events.
For this reason I propose to:
* Rewrite Commons JCS to use the Log4j API directly.
* Deprecate the logging wrapper and related methods (e.g. {{JCS.setLogSystem}})
for removal in the next major version.
Regarding the choice of the backend: the Log4j API implements all the features
JCS needs (like lazy formatting of the message) and if users want to use JUL as
backend, it is fairly easy to do so. On the other hand redirecting log events
from JUL to any other logging backend is a PITA.
> Use System.Logger abstraction
> -----------------------------
>
> Key: JCS-241
> URL: https://issues.apache.org/jira/browse/JCS-241
> Project: Commons JCS
> Issue Type: Improvement
> Reporter: Piotr Karwasz
> Assignee: Piotr Karwasz
> Priority: Minor
>
> Commons JCS contains a logging wrapper in {{o.a.c.jcs3.log}}.
> Using a logging wrapper causes several issues:
> * Users need to set the hard to find {{jcs.logSystem}} system property to
> switch between the JUL and Log4j API backend.
> * Both backends lose location information, which will always point to the
> wrapper class as source of all log events.
> For this reason I propose to:
> * Rewrite Commons JCS to use the System.Logger API directly.
> * Deprecate the logging wrapper and related methods (e.g.
> {{JCS.setLogSystem}}) for removal in the next major version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
