logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4J2-730) Log4jContextFactory selector discovery logic is not extensible
Date Wed, 06 Aug 2014 13:33:11 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Remko Popma resolved LOG4J2-730.

       Resolution: Fixed
    Fix Version/s: 2.0.2

Fixed in revision 1616231.
Please verify and close.

> Log4jContextFactory selector discovery logic is not extensible
> --------------------------------------------------------------
>                 Key: LOG4J2-730
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-730
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0
>            Reporter: Mariano Gonzalez
>            Assignee: Remko Popma
>             Fix For: 2.0.2
> I want to write my own LoggerContextFactory which forces my specific instance of ContextSelector
and sets some system properties. 
> I'd like to extend Log4jContextFactory class to just add this logic and reuse the rest
of the code, however that doesn't seem possible since the selector attribute is private and
the piece of code that fetches it is embedded in the constructor.
> I think it makes sense to have the selector as a private field, but if the code to fetch
it could be a protected one so that it can be overridden, that would enable use cases like
> Thanks

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