Home/ Questions/Q 8211103
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T10:18:55+00:00

It was supposed to be released with Java 7, but the status is Dormant

  • 0

It was supposed to be released with Java 7, but the status is Dormant. On the other hand, the same page says

Use generics in the JMX API, for example have MBeanServer.queryNames return Set<ObjectName> rather than just Set.

and this did happen in Java 6. So, did some of the changes get in? Are there significant differences between Java 6 and Java 7 JMX implementations? Looking at Javadocs, I didn’t notice any, but this only covers the API.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I asked this question also to the current product manager for JMX at Oracle, Tuva Palm some times ago (September 2011), and she promised me, that JMX 2.0 is not dead and there will be a technical roadmap in Q1/2012.

    However, nothing have happened until now and even worse, JSR-255, the JMX 2.0 spec (but also JSR-262, ther WebService connector stuff) has been marked as withdrawn since 2016 with the following 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. (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.

    So JMX 2.0 in its original form is factually dead.

    • 0