• JSRs by Platform
• JSRs by Technology
• JSRs by Stage
• JSRs by Committee
• List of All JSRs



Register for Site

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy


• About JCP
  • Program Overview
  • JCP Process Document
  • Calendar
  • JCP Members
  • Executive Committee
  • Elections
• Get Involved
  • Overview
  • Becoming a JCP Member
  • Java in Education
• Community Resources
  • Overview
  • Tutorials
  • JCP Podcasts
  • Spec Lead Guide
  • TCK Tool & Info
  • License Reference
• Community News
  • News
  • Programs & Awards
  • Press Releases
  • Success Stories
• FAQ
• Contact Us

Proposed Changes for JSR 3 Maintenance Review 6

Hinkmond Wong, JSR 3 Maintenance Lead

Summary of the proposed specification changes

1. Add announcement to subsume into JDK Platform:

Announcement

Since JSR 3, JMX has been distributed as a standalone technology and part of the Java SE at the same time, the JMX API has become stable (no significant changes) for a long time and the need to use newer releases of the JMX 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 Standalone distribution. After this MR, JMX 1.4, the technology that JSR 3 defines, will be delivered as a part of the Java SE solely. Future changes in the JMX API will be defined through the Platform JSR.

The subsumption of the JMX into the Platform JSR does not change any mechanisms defined in JMX. The interfaces are the same except that they will then be directly specified in the Platform JSR. Deployment of alternative implementations of the JMX 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