JDK-4886011 : Modify toString() of queries so it is reversible
- Type: Enhancement
- Component: core-svc
- Sub-Component: javax.management
- Affected Version: 1.2.0,5.0
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- OS: generic,windows_2000
- CPU: generic,x86
- Submitted: 2003-07-02
- Updated: 2008-01-24
- Resolved: 2008-01-24
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.
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 :
|
Description
It should be possible to take a QueryExp consisting only of standard JMX classes and produce a string from it that can be parsed to reconstruct the original QueryExp. This is particularly useful for JSR 160 (JMX Remote API) connectors based on text protocols such as SOAP. The client side of such a connector presents the MBeanServerConnection interface, including methods queryNames and queryMBeans. These methods are invoked with an object of type QueryExp. Most such objects are manufactured by static methods in the Query class, and are of non-public classes. So it is not possible to introspect the query portably in any way other than toString() or serialization. If the toString() of the standard QueryExp classes in the JMX RI were reversible, we could propose it as an informal standard to other implementors.
Comments
|