JMX API Enhancements
There were no API changes to JMX in Java SE 7.
- Generification.
The JMX API now fully supports Generics.
ObjectName supports wildcards.
key=* wildcards are now supported in ObjectName.
Previously, "domain:key1=value1,*" could be used to
match MBeans that have key1=value1 in their name, but
"domain:key1=*" could not be used to match MBeans that
have key1 in their name. This is now possible.
- New
JMX class.
A new class, javax.management.JMX,
has been added to house constants and static methods.
- MBean Descriptors added.
MBean Descriptors have been added. Descriptors allow you to give
additional information about MBeans to management clients. See
MBean Descriptors
in the JMX Technology Tutorial for information.
- MXBeans added.
MXBeans have been added. MXBeans are MBeans that provide a
convenient way to bundle related values together without requiring
clients to be specially configured to handle the bundles. A defined
set of MXBeans already existed in the J2SE 5.0 platform, but Java
SE 6 introduces an API to allow you to program your own custom
MXBeans. See Introducing MXBeans in the
JMX Technology Tutorial for information.
- JMX Monitor API now supports complex types.
Improvements have been made to the JMX
Monitor API to support complex types. Previously, only
attributes of simple types could be monitored, but often, the value
to be monitored is buried inside a more complex type. See the
JMX Specification, version
1.4, for details of the behavior of monitors.
The Java Management Extensions (JMX) technology became a part of
the Java platform in the Java 2 Platform, Standard Edition (J2SE)
5.0.
