logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-589) Allow filtering on custom levels in configuration
Date Fri, 26 Sep 2014 02:11:34 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148624#comment-14148624

Ralph Goers commented on LOG4J2-589:

I would also argue that it is a good practice to place a list of items in a container and
not have them just arbitrarily appear in some unrelated element. Another way of looking at
it is that with the CustomLevels element I would expect to see a List<CustomLevel> (or
similar) declared in the Configuration object.  With CustomLevels just appearing there I don't
have any idea where or how they are stored.  Furthermore, I think something like Jackson would
have a hard time with it.

> Allow filtering on custom levels in configuration
> -------------------------------------------------
>                 Key: LOG4J2-589
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-589
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Configurators
>    Affects Versions: 2.0-rc1
>            Reporter: James Hutton
>            Assignee: Remko Popma
>              Labels: configuration, custom, level
>             Fix For: 2.1
> Previous title: Use forName instead of getLevel and valueOf for configuration
> Without this one cannot use custom log levels in configuration without forking a large
amount of code.  Either the forName method needs to be removed and custom log levels should
be explicitly forbidden, or support should be consistent.
> Classes that would need to be modified:
> BaseConfiguration, NullConfiguration, and DefaultConfiguration.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message