[
https://issues.apache.org/jira/browse/LOG4J2-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner updated LOG4J2-2010:
------------------------------------
Description:
Class paths are currently split into a hierarchy of loggers. Private classes
however are not put as a child of their containing class logger because their
classpath contains a dollar sign ($). To allow this usecase it has been
discussed to add a logger hierarchy calculation strategy that determines how
the logger hierarchy is built from a classpath.
By default the default implementation of the hierarchy calculations strategy
should split a class path by a dot (.). It should further allow splitting by
other common separators like a dollar and a slash ($ and /) to accomodate more
use cases. It should also be possible to split by multiple separator characters
at the same time, meaning that the logger hierarchy could be split by either a
dot, a dollar or a slash or arbitrary other characters as well.
It is yet to be discussed whether we the user should be able to provide a
custom implementation of the hierarchy calculation strategy. If so, the
configuration of that strategy must allow the class notation. If the user
cannot provide a custom implementation, the following configuration syntax
should suffice as suggested by Gary:
{code}
<Configuration hierarchySeparators="./$" ...
{code}
while the default configuration would be:
{code}
<Configuration hierarchySeparators="." ...
{code}
was:
Class paths are currently split into a hierarchy of loggers. Private classes
however are subclassed into their containing class with a dollar sign ($) which
is currently not reflected as an entry in the logger hierarchy. It has been
discussed to allow the customization of the logger hierarchy calculation
strategy.
By default the default implementation of the hierarchy calculations strategy
should split a class path by a dot (.). It should further allow splitting by
other common separators like a dollar and a slash ($ and /) to accomodate more
use cases. It should also be possible to split by multiple separator characters
at the same time, meaning that the logger hierarchy could be split by either a
dot, a dollar or a slash or arbitrary other characters as well.
It is yet to be discussed whether we the user should be able to provide a
custom implementation of the hierarchy calculation strategy. If so, the
configuration of that strategy must allow the class notation. If the user
cannot provide a custom implementation, the following configuration syntax
should suffice as suggested by Gary:
{code}
<Configuration hierarchySeparators="./$" ...
{code}
while the default configuration would be:
{code}
<Configuration hierarchySeparators="." ...
{code}
> Allow customization of the conversion from logger names to logger hierarchy
> ---------------------------------------------------------------------------
>
> Key: LOG4J2-2010
> URL: https://issues.apache.org/jira/browse/LOG4J2-2010
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Reporter: Dominik Psenner
> Priority: Minor
>
> Class paths are currently split into a hierarchy of loggers. Private classes
> however are not put as a child of their containing class logger because their
> classpath contains a dollar sign ($). To allow this usecase it has been
> discussed to add a logger hierarchy calculation strategy that determines how
> the logger hierarchy is built from a classpath.
> By default the default implementation of the hierarchy calculations strategy
> should split a class path by a dot (.). It should further allow splitting by
> other common separators like a dollar and a slash ($ and /) to accomodate
> more use cases. It should also be possible to split by multiple separator
> characters at the same time, meaning that the logger hierarchy could be split
> by either a dot, a dollar or a slash or arbitrary other characters as well.
> It is yet to be discussed whether we the user should be able to provide a
> custom implementation of the hierarchy calculation strategy. If so, the
> configuration of that strategy must allow the class notation. If the user
> cannot provide a custom implementation, the following configuration syntax
> should suffice as suggested by Gary:
> {code}
> <Configuration hierarchySeparators="./$" ...
> {code}
> while the default configuration would be:
> {code}
> <Configuration hierarchySeparators="." ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
