• 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

Change Log for JSR 160 Maintenance Review 2

Éamonn McManus, JSR 160 Maintenance Lead

This is the Change Log for the second Maintenance Review of JSR 160. Questions and comments on this Change Log should be directed to jmx-spec-comments@sun.com.

This Maintenance Review defines version 1.4 of the JMX Remote API as originally defined by JSR 160. In the previous Maintenance Review, the API version number jumped from 1.0 to 1.3 to match the numbering of the JMX API, JSR 3, so versions 1.1 and 1.2 have never existed.

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.

• 6343209: Specify how SubjectDelegationPermission works for ConnectorServer creators.

  The creator of a JMXConnectorServer no longer needs to have all the permissions that connection created by the connector server will use. It can have a SubjectDelegationPermission for each remotely-authenticated identity instead. This simplifies deployment in security-conscious environments.

• 5021246: Spec for RMI connector should say code downloading used if applicable.

  The RMI connector will use code downloading as specified in the article Dynamic code downloading using Java RMI if applicable. The Reference Implementation has always behaved this way, and the specification has been updated to reflect that.

• 6375696: CORBA tie classes for JMX Remote API should be in javax.management.remote.rmi

  For compliance with the OMG's "IDL to Java Language Mapping Specification", the CORBA "tie classes" for the remote objects javax.management.remote.rmi.RMIServerImpl and javax.management.remote.rmi.RMIConnectionImpl should be in the javax.management.remote.rmi package.