JDK-6602310 : Extensions to Query API for JMX 2.0
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 1.2.0,5.0,6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_2000
  • CPU: generic,x86
  • Submitted: 2007-09-07
  • Updated: 2017-05-16
  • Resolved: 2011-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
7 b25Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
A number of extensions to the JMX Query API are under consideration for its version 2.0, being defined by JSR 255.  Among these are:

- Define a query language and provide methods to convert strings in this language into QueryExp objects and vice versa.

- Define a way to get the string representation (String.valueOf) of an arbitrary attribute inside a query.  Currently only attributes of type Number, String, or Boolean can figure in queries.

- Allow attribute names inside queries to contain a dot, to extract a value from within a complex attribute, as is already done in the Monitor API.

EVALUATION For the moment we are not planning to add the "attribute as string" feature. The main use case for this was ObjectName attributes, but the ability to access properties using dot syntax means that you can write objectNameAttr.canonicalName to access the ObjectName as a string via ObjectName.getCanonicalName(). The other items are still planned as described.

EVALUATION A relatively small but powerful set of extensions.