-
Enhancement
-
Resolution: Fixed
-
P3
-
1.2.0, 5.0, 6
-
b25
-
generic, x86
-
generic, windows_2000
-
Verified
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.
- 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.
- duplicates
-
JDK-4886011 Modify toString() of queries so it is reversible
- Closed
- relates to
-
JDK-6610917 Define a generic NotificationFilter
- Closed
-
JDK-6658153 Remarks about the Extensions to Query API for JMX 2.0
- Closed
-
JDK-6701498 Change JMX query language to use * and ? as wildcards rather than % and _
- Closed
-
JDK-5072268 Suggested API changes for JMX 2.0
- Closed