hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Bowman (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ZOOKEEPER-99) All MXBeans interfaces that don't use complex paramters need to be renamed as MBean interaces.
Date Fri, 27 Feb 2009 11:45:12 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Eric Bowman updated ZOOKEEPER-99:

    Attachment: ZOOKEEPER-99.patch

Here's a patch against r748487.

This problem is quite an obstacle to embedding Zookeeper in JBoss, so it would be great if
you could roll it into 3.2.

The JMX convention (as implemented by JBoss, anyhow) requires that the MBean interfaces be
named XXXMBean, and the implementing classes XXX.

So I have renamed, for example, ZooKeeperServerMXBean to ZooKeeperServerBeanMBean, so that
ZooKeeperServerBean can remain.

I also made all the MBean interfaces extend ZKInfoMBean (formerly ZKMBeanInfo), instead of
having each implementation implement it as well.  I suppose that might controversial, but
I couldn't see a good reason to have ZKInfoMBean references scattered around the implementation.

Hope this is useful -- it's necessary for us to use ZooKeeper, so we will be working off a
patched version of the trunk until this or something equivalent makes its way into a release.

> All MXBeans interfaces that don't use complex paramters need to be renamed as MBean interaces.

> -----------------------------------------------------------------------------------------------
>                 Key: ZOOKEEPER-99
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-99
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: jmx
>            Reporter: Hiram Chirino
>         Attachments: ZOOKEEPER-99.patch
> All the MXBean interfaces that I've looked at are standard MBean interfaces.  The interface
names should get renamed to MBean instaead of MXBean. That way the server can also run on
a the Java 1.5 Platform.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message