db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3540) Document the JMX management and monitoring functionality
Date Fri, 04 Apr 2008 18:29:25 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585685#action_12585685
] 

John H. Embretsen commented on DERBY-3540:
------------------------------------------

Good observation, Kim. The permission syntax for MBeanPermission is indeed a bit unusual.
But it is correct as written. This is documented in the API for MBeanPermission, e.g. at http://java.sun.com/j2se/1.5.0/docs/api/javax/management/MBeanPermission.html


<quote>
The class name, member, and object name can be written together as a single string, which
is the name of this permission. The name of the permission is the string returned by getName().
The format of the string is:
className#member[objectName]
(...)
If the member is omitted, the # may be too (but does not have to be).(...)
</quote>

Furthermore, the objectName may include wildcards, as in our suggestion. This will include
all MBeans in the "org.apache.derby" domain (the domain is what is before the colon (:) inside
the brackets).


> Document the JMX management and monitoring functionality
> --------------------------------------------------------
>
>                 Key: DERBY-3540
>                 URL: https://issues.apache.org/jira/browse/DERBY-3540
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, JMX
>    Affects Versions: 10.4.0.0
>            Reporter: John H. Embretsen
>            Assignee: Kim Haase
>         Attachments: cadminconfig86869.html, cadminconfig86869.html, cdevbabejgjd.html,
ctunsetprop824983.html, DERBY-3540-1.diff, DERBY-3540-2.diff, DERBY-3540-3.diff, tadminconfigsysteminformation.html
>
>
> Brand new management and monitoring capabilities using JMX were starting to be added
to Derby in the first calendar quarter of 2008. This issue tracks efforts documenting this
functionality.
> A JMX M&M functional specification document (funcSpec.html) is attached to DERBY-1387.
More information may be available on the wiki - http://wiki.apache.org/db-derby/DerbyJMX -
and in JMX-related Javadocs ("published API") (packages org.apache.derby.mbeans and org.apache.derby.mbeans.drda).

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


Mime
View raw message