Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 91824 invoked from network); 12 Mar 2008 15:10:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2008 15:10:23 -0000 Received: (qmail 81142 invoked by uid 500); 12 Mar 2008 15:10:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 81115 invoked by uid 500); 12 Mar 2008 15:10:20 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 81104 invoked by uid 99); 12 Mar 2008 15:10:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2008 08:10:20 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2008 15:09:40 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 02405234C098 for ; Wed, 12 Mar 2008 08:08:50 -0700 (PDT) Message-ID: <425310043.1205334530008.JavaMail.jira@brutus> Date: Wed, 12 Mar 2008 08:08:50 -0700 (PDT) From: "John H. Embretsen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3385) Tests for JMX Management and Monitoring In-Reply-To: <16980351.1202127307854.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577868#action_12577868 ] John H. Embretsen commented on DERBY-3385: ------------------------------------------ Ah, so I don't really need to use DatabaseMetaData.... Much better, I will create a new patch with this change (using the Driver interface directly). It still does not necessarily access the exact same embedded driver as the MBean implementation, but I have no idea how to access the embedded driver in a remote VM. It is better than using the client driver though, I guess. > Tests for JMX Management and Monitoring > --------------------------------------- > > Key: DERBY-3385 > URL: https://issues.apache.org/jira/browse/DERBY-3385 > Project: Derby > Issue Type: Sub-task > Components: JMX, Test > Reporter: John H. Embretsen > Assignee: John H. Embretsen > Attachments: d3385_ant-junit-all.diff, d3385_jdbcMBeanTest_01.diff, d3385_jdbcMBeanTest_02.diff, d3385_versionMBeanTest_01.diff, d3385_versionMBeanTest_02.diff, TestJMXp9.java > > > DERBY-1387 implements a new feature set in Derby: Java Management eXtentions (JMX), i.e. standards-based management and monitoring capabilities. > As these are completely new features providing additional interfaces to a running Derby system, a set of functional regression tests should be added. The new tests should verify that Derby's public JMX API works as intended, and should be able to detect regressions in this area in the future. There is a functional specification (jmxFuncspec.html) attached to DERBY-1387 which may be used as reference. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.