JDK-6694049 : Document that some types of query are only available if the other end is sufficiently recent
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-25
  • Updated: 2010-07-29
  • Resolved: 2008-11-13
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.
JDK 7
7Resolved
Related Reports
Duplicate :  
JDK-6750008 - Add JMX.getSpecificationVersion(MBeanServerConnection) and document interop constraints
Description
The set of available standard JMX queries (javax.management.QueryExp) has expanded slightly over time.  The original set was defined in version 1.0 of the JMX API, way back in 2000.  It remained unchanged through to 1.2, which was included with Java SE 5.0.

In Java SE 6 we added Query.isInstanceOf, which is documented with a @since tag.

In version 2.0 of the JMX API, we're including the ability to use dotted attribute expression like A.b.c, with the same meaning as for monitors (see javax.management.monitor).  We need to document clearly that this capability is not available if you are connected to a remote agent that has an earlier version of the JMX API.
Comments
EVALUATION Fixed while adding JMX.getSpecificationVersion.
13-11-2008
EVALUATION This should at least be mentioned in Query.attr and in AttributeValueExp.getAttribute. We should probably also add something to the introductory text for the Query class that mentions the possible interoperation problems for dotted attribute expressions and for isInstanceOf.
25-04-2008