[
https://issues.apache.org/jira/browse/DERBY-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5637:
-----------------------------
Attachment: DERBY-5637-2.zip
DERBY-5637-2.stat
DERBY-5637-2.diff
Attaching DERBY-5637-2.diff, DERBY-5637-2.stat, and DERBY-5637-2.zip, with
further changes to 9 files:
M src/adminguide/cadminjmxoverview.dita
M src/adminguide/radminjmxcode.dita
M src/adminguide/radminjmxdisable.dita
M src/adminguide/radminjmxenablenoauth.dita
M src/adminguide/radminjmxenablepwd.dita
M src/adminguide/radminjmxenablepwdssl.dita
M src/adminguide/radminjmxintro.dita
M src/adminguide/radminjmxjconsole.dita
M src/adminguide/radminjmxtroubleshoot.dita
I hope I've incorporated your suggestions. I didn't remove the parts marked
"not public" in the MBeans info, but instead changed them to "not in the public
API" for clarity. The non-public API is not really hidden, since anyone can
check out the code and take a look. Does this make sense? I can remove those
items completely if you prefer.
I found more occurrences of "6 or 7" and changed them to "6 or later".
The Java SE documentation uses "platform MBean server" so I made the usage
consistent with that.
Thanks again for the great review -- even catching the capitalized "It" in
midsentence.
> Document Derby's JMX capabilities and how to disable them
> ---------------------------------------------------------
>
> Key: DERBY-5637
> URL: https://issues.apache.org/jira/browse/DERBY-5637
> Project: Derby
> Issue Type: Improvement
> Components: Documentation, JMX
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5637-2.diff, DERBY-5637-2.stat, DERBY-5637-2.zip,
> DERBY-5637.diff, DERBY-5637.stat, DERBY-5637.zip
>
>
> Derby's JMX beans are useful, although limited. We should document their
> capabilities as well as how to disable/restrict access to them in
> security-conscious environments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
