JMX 2.0的状态是什么？ [英] What is the status of JMX 2.0?

问题描述

它本应与Java 7一起发布，但状态为 Dormant 。另一方面，同一页面说

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

在JMX API中使用泛型，例如 MBeanServer.queryNames 返回设置< ObjectName> 而不仅仅是设置。

这确实发生了在Java 6中。那么，是否有一些变化进入？ Java 6和Java 7 JMX实现之间是否存在显着差异？看看Javadocs，我没有注意到任何问题，但这只涉及API。

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.

推荐答案

我也问过这个问题Oracle的JMX现任产品经理，很久以前（2011年9月） Tuva Palm ，她承诺我，JMX 2.0并没有死，2012年第一季将会出现技术路线图。

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.

然而，直到现在都没有发生任何事情，更糟糕的是， JSR-255 ，JMX 2.0规范（还有 JSR自2016年起，-262 ，其他WebService连接器内容已被标记为撤回出于以下原因：

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指定对javax.management。*的更改，由于缺乏资源而随后被放弃，并且不是包含在Java SE 6或7平台中。 （这些更改与JSR 3,160和336指定的javax.management。*的其他更改不同，以包含在Java SE 6和7平台中。）2014年确定将直接指定未来对JMX技术的更改来自Java SE平台的伞形JSR。

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.

因此原始形式的JMX 2.0实际上已经死了。

So JMX 2.0 in its original form is factually dead.

这篇关于JMX 2.0的状态是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！