This is the Change Log for the first Maintenance Review of JSR 160. Questions and comments on this Change Log should be directed to firstname.lastname@example.org.
This Maintenance Review defines version 1.3 of the JMX Remote API as originally defined by JSR 160. The API version number jumps from 1.0 to 1.3 to match the numbering of the JMX API, JSR 3.
The 7-digit code numbers associated with each change are identifiers in the public bug database at bugs.sun.com.
A larger set of updates to the JMX Remote specification is planned as part of JSR 255, "JMX Specification, version 2.0". The changes proposed in this Maintenance Review are intended as interim steps towards JSR 255. These changes have all been approved by the JSR 255 Expert Group.
An updated standalone TCK will be available that reflects the changes in this Maintenance Review. In addition, it is intended that these changes will be included in the Java SE 6 ("Mustang") release.
The following changes are made to the specification generated by the Javadoc tool.
6231888: JMXConnector implements Closeable
java.io.Closeable defines the single method
public void close() throws IOException;
JMXConnector contains a method with the
same signature, the
can extend the
6234398: JMX connection provider API exception
handling unclear. The interfaces
JMXConnectorServerProvider are clarified
so that methods throw
if the protocol in the URL is not recognized by the
JMXProviderException if this is the right
provider for the URL but it cannot be used for some
reason, and some other
IOException in other
6238076: Serialized form of
clientNotifID field. This field was
inadvertently included in the serial form. Its purpose is to track the
notification sequence number in
JMXConnectionNotifications from the
typically only serialized if it is the value returned by
RMIConnectorServer.toJMXConnector, in which case it will not
have been connected and will have a sequence number of
0. Even if an
RMIConnector is serialized in other
circumstances, there is little or no interest in continuing
the notification sequence numbers when it is subsequently
6238815: Add a way to get the address to which a
connector client is connected. The new interface
JMXAddressable can be implemented by a
given connector client. When this is so, users can cast the
JMXConnector instance to
JMXAddressable and call
getAddress() to discover the address to which
the client is connected. RMI client connectors are
specified to implement this interface. The
JMXConnectorServer class also implements
this interface, via its existing