[jira] [Created] (LOG4J2-530) JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean server

["Remko Popma (JIRA)" <ji...@apache.org>]

Remko Popma created LOG4J2-530:
----------------------------------

             Summary: JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean server
                 Key: LOG4J2-530
                 URL: https://issues.apache.org/jira/browse/LOG4J2-530
             Project: Log4j 2
          Issue Type: New Feature
          Components: JMX
    Affects Versions: 2.0-beta9, 2.0-rc1
            Reporter: Remko Popma
            Assignee: Remko Popma


Currently the Log4J2 JMX Client GUI will take a snapshot of the MBean server state when the client GUI is started. The GUI displays a tab for each LoggerContextAdmin MBean that existed at startup time. 

This is a static snapshot: these tabs do not change if the LoggerContext MBean is unregistered while the GUI is active. Also, if additional LoggerContext MBeans are registered after the GUI was started, the GUI will not be "aware" of this and will not display new tabs for the added LoggerContext.

This ticket is a request to dynamically update the GUI in response to LoggerContext MBeans being registered/unregistered after the GUI was started.
* newly added LoggerContexts should result in a new tab being added for each new LoggerContext
* if MBeans for a LoggerContext are unregistered from the server, the corresponding tab should be removed from the GUI



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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