Proposed Changes for JSR 160 Maintenance Review 3

Hinkmond Wong, JSR 160 Maintenance Lead

Summary of the proposed specification changes.

1. Add announcement to subsume into JDK Platform:


Since JSR 160, JMX Remote API has been distributed as a standalone technology and part of the Java SE at the same time, the JMX Remote API has become stable (no significant changes) for a long time and the need to use newer releases of the JMX Remote API with shipping releases of Java SE has mostly disappeared in recent years.

In accordance with the JCP 2.9 Process, we are announcing the end of JMX Remote API Standalone distribution. After this MR, JMX Remote API 1.4, the technology that JSR 160 defines, will be delivered as a part of the Java SE solely. Future changes in the JMX Remote API will be defined through the Platform JSR.

The subsumption of the JMX Remote API into the Platform JSR does not change any mechanisms defined in JMX Remote API. The interfaces are the same except that they will then be directly specified in the Platform JSR. Deployment of alternative implementations of the JMX Remote API will continue to be supported.

2. Change last paragraph in section 1.2.3 to:

As this annotation does not exist in Java SE 5.0 or subset Profiles of Java SE 8.0 that do not include the java.beans package, then the behavior specified does not apply

3. Delete JRMP definition in section 14.1

4. Clarify RMI connector support in setion 14.1 to:

The RMI Connector supports the JRMP transport and optionally the IIOP transport

5. Change URLs to URLS:
Section 17.4.4:


6. Change references to Sun Microsystems to Oracle.