You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2015/04/24 01:59:38 UTC
[jira] [Resolved] (LOG4J2-998) Make
org.apache.logging.log4j.core.Logger#updateConfiguration protected
[ https://issues.apache.org/jira/browse/LOG4J2-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory resolved LOG4J2-998.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.3
Sounds reasonable. [~ralphgoers] might offer another POV on such a thing but making the method protected seems OK.
Please verify and close this ticket.
> Make org.apache.logging.log4j.core.Logger#updateConfiguration protected
> -----------------------------------------------------------------------
>
> Key: LOG4J2-998
> URL: https://issues.apache.org/jira/browse/LOG4J2-998
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.1
> Reporter: Mariano Gonzalez
> Fix For: 2.3
>
>
> Hello,
> I'm using log4j2 as the foundation for a centralized logging infrastructure inside an application container. For such requirement, I need to be able to override the org.apache.logging.log4j.core.Logger#updateConfiguration method. However, that method has package visibility and thus cannot be gracefully overriden.
> It'd be great if that method could be protected so that subclasses can redefine it.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org