- #255 255 255 0 UPDATE#
Access to the objects is then exclusively through the MBean Server. JSR 3 (JMX API) defined a way to create named objects called MBeans (managed beans) or managed objects, and to store those objects in a repository called the MBean Server. 2.7 Please give a short description of the underlying technology or technologies: Another aim is to incorporate changes and new features whose desirability has become clear since version 1.2 was completed in 2002.
#255 255 255 0 UPDATE#
One important aim of this JSR is to update the API so that it takes advantage of generics and annotations to provide a simpler programming model. The version of the JMX API that was incorporated into Tiger was identical to the standalone version 1.2 produced by a Maintenance Review of JSR 3. 2.6 Why isn't this need met by existing specifications? Improved functionality of the existing JMX APIs and better ease-of-use. 2.5 What need of the Java community will be addressed by the proposed specification? Should this JSR be voted on by both Executive Committees? Changes to improve this API will therefore be useful on the J2EE platform in addition to the J2SE platform.莫lthough some investigations have been done concerning the use of the JMX API on certain configurations of the J2ME platform, there are no current plans to standardize that. The J2EE platform includes a specification (JSR 77) based on the JMX API, and most if not all implementations of this platform use the JMX API extensively. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions. 2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.) It is a key goal of this JSR to be incorporated into version 6.0 of the J2SE platform (Mustang), and this might mean that some of these proposed changes end up being postponed to a later JSR. * Support cascaded (federated) MBean Servers. * Generalize monitors so that they can monitor attributes that are not simple types, and so that their thresholding is customizable. * Make Open MBeans easier to use to address interoperability and versioning concerns. * Use annotations to make writing MBeans easier. * Use generics in the JMX API, for example have MBeanServer.queryNames return Set rather than just Set. This specification will update the JMX and JMX Remote APIs to improve existing interfaces, notably with respect to ease-of-use, and to add new functionality whose usefulness has become clear since those APIs were completed. Submitting Member: Sun Microsystems, Inc.蘑.1 Please describe the proposed Specification: Original Java Specification Request (JSR) Maintenance Lead: Staffan Larsen, Oracle America蘑006.01.20: This JSR is now scheduled for Dolphin (Java SE 7) and not Mustang. Staffan Larsen is the new Maintenance Lead. The following information has been updated from the original JSR: Updates to the Java Specification Request (JSR) Please direct comments on this JSR to the Spec Lead(s) It will improve usability of existing features and add new functionality. This JSR updates the JMX and JMX Remote APIs for version 6.0 of the Java(TM) Platform, Standard Edition.
Java Specification Participation Agreement version in use: 2.0 (The changes were distinct from other changes to javax.management.* specified by JSRs 3, 160, and 336 for inclusion in the Java SE 6 and 7 Platforms.) It was determined in 2014 that future changes to JMX technology would be specified directly by the umbrella JSR for the Java SE Platform. Reason: JSR 255 specified changes to javax.management.* which were subsequently abandoned due to lack of resources, and were not included in the Java SE 6 or 7 Platforms.