[jira] [Commented] (LOG4J2-1206) org.apache.logging.log4j.core.LoggerContext#updateLoggers should call firePropertyChangeEvent

["Rodrigo Merino (JIRA)" <ji...@apache.org>]

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

Rodrigo Merino commented on LOG4J2-1206:
----------------------------------------

[~jvz] That change looks good to me. It's okay if it's up to the listener to get the particularity of the configuration it is interested in.

> org.apache.logging.log4j.core.LoggerContext#updateLoggers should call firePropertyChangeEvent
> ---------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1206
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1206
>             Project: Log4j 2
>          Issue Type: Wish
>          Components: Core, JMX
>    Affects Versions: 2.1
>         Environment: All
>            Reporter: Rodrigo Merino
>              Labels: features
>         Attachments: LOG4J2_1206___org_apache_logging_log4j_core_LoggerContext_updateLoggers_should_call_firePr.patch
>
>
> Currently, only notifications for whole config changes are being fired (in org.apache.logging.log4j.core.LoggerContext#setConfiguration), but since particular loggers are allowed to be changed (i.e.: through JMX, which calls org.apache.logging.log4j.core.LoggerContext#updateLoggers), there should be a way to be notified about those changes too.
> The fired event should ideally contain specific information about what logger(s) changed and what change it was.



--
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