[
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.
