Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 9 Sep 2015 13:30:45 +0000 (UTC)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12862756.1441805394000.290370.1441805445693@Atlassian.JIRA>
In-Reply-To: <JIRA.12862756.1441805394000@Atlassian.JIRA>
References: <JIRA.12862756.1441805394000@Atlassian.JIRA>
 <JIRA.12862756.1441805394285@arcas>
Subject: [jira] [Created] (DERBY-6832) Derby JMX Beans could be made
 self-describing for tools like JConsole
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bryan Pendleton created DERBY-6832:
--------------------------------------

             Summary: Derby JMX Beans could be made self-describing for tools like JConsole
                 Key: DERBY-6832
                 URL: https://issues.apache.org/jira/browse/DERBY-6832
             Project: Derby
          Issue Type: Improvement
          Components: JMX
    Affects Versions: 10.12.0.0
            Reporter: Bryan Pendleton
            Priority: Minor


Derby's JMX management beans, such as the cache-related
beans created by DERBY-6733, could be more useful if they
included some amount of internal documentation as part of
the beans themselves, perhaps by implementing the
getDescription apis defined by the StandardMBean
(http://docs.oracle.com/javase/7/docs/api/javax/management/StandardMBean.html).

Another possible approach is described in this article, using
annotation facilities:
https://weblogs.java.net/blog/emcmanus/archive/2005/07/adding_informat.html

If the beans included this sort of information, tools like JConsole would
provide more information for users who are just getting started learning
about these beans and how they work.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)