[
https://issues.apache.org/jira/browse/LOG4J2-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507797#comment-14507797
]
Mariano Gonzalez commented on LOG4J2-998:
-----------------------------------------
Hello Gary,
Basically I have this class, which is a wrapper that I used on Loggers which
are shared across many applications to make sure that the message is logged
into the correct context:
https://github.com/mulesoft/mule/blob/mule-3.x/modules/launcher/src/main/java/org/mule/module/launcher/log4j2/DispatchingLogger.java
The problem is that if the configuration is reloaded (most likely because the
user modified the log4j2.xml) file, I need the
updateConfiguration(Configuration) invokation to be propagated to the
originalLogger. Because that method is not visible from this context, I cannot
override it without hacking.
Thanks
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
