JDK-6477850 : jhat OQL Support direct value of java.lang.String type fields
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 6
  • Priority: P5
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_10
  • CPU: sparc
  • Submitted: 2006-10-03
  • Updated: 2011-03-08
  • 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.
JDK 6 JDK 7
6u1Fixed 7 b03Fixed
Description
A DESCRIPTION OF THE REQUEST :
Currently one has to use stringTypeValue.value.toString() javascript expression to get the string form of the value of java.lang.String typed fields.

This could be implemented by a sub class of

com.sun.tools.hat.internal.model.JavaObject

something like:

com.sun.tools.hat.internal.model.JavaStringObject

This is similar to what JDI does by having:

com.sun.jdi.StringReference

as a sub interface of:

com.sun.jdi.ObjectReference


JUSTIFICATION :
Awkward usage.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
For java.lang.String type values support direct mechanism.

I should be able to use:

select file.path
    from java.io.File file

ACTUAL -
I have to use:

select file.path.value.toString()
    from java.io.File file

which is very awkward.


---------- BEGIN SOURCE ----------
OQL Query:

select file.path.value.toString()
    from java.io.File file
---------- END SOURCE ----------

Comments
EVALUATION Need to be fixed.
01-11-2006