[logback-dev] [JIRA] Updated: (LBCLASSIC-61) JMXConfigurationAction should allow a configurable ObjectName.

[Ceki Gulcu (JIRA)]

     [ http://jira.qos.ch/browse/LBCLASSIC-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu updated LBCLASSIC-61:
--------------------------------

    Priority: Critical  (was: Major)

> JMXConfigurationAction should allow a configurable ObjectName.
> --------------------------------------------------------------
>
>                 Key: LBCLASSIC-61
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-61
>             Project: logback-classic
>          Issue Type: Improvement
>    Affects Versions: 0.9.9
>            Reporter: Anders Engström
>            Assignee: Ceki Gulcu
>            Priority: Critical
>         Attachments: jmxConfigurator.patch.gz
>
>
> Currently there is no way to customize the ObjectName the MBean is bound to (besides using a ContextSelector - which can be a hassle).
> This is an issue when deploying several applications in the same JVM (read: multiple web-applications in the same servlet engine).
> This patch modifies JMXConfiguratorAction to accept two additional attributes that allow customizing the ObjectName for the MBean:
> <jmxConfigurator/>
> This yields the default ObjectName of "ch.qos.logback.classic:Name=${nameOfContext},Type=ch.qos.logback.classic.jmx.Configurator".
> <jmxConfigurator namespace="foo"/>
> This results in "ch.qos.logback.classic:Name=${nameOfContext},Type=ch.qos.logback.classic.jmx.Configurator,Namespace=foo".
> <jmxConfigurator objectName="logback:name=foo,type=bar"/>
> Which obviously results in "logback:name=foo,type=bar" :)
> Let me know if I need to adjust the patch in any way.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira