JDK-4176246 : JVMDI spec: Redefine classes needs to distinguish unsupported version error
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 1.2.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1998-09-24
  • Updated: 2001-01-17
  • Resolved: 2001-01-17
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.
Other
1.4.0 betaFixed
Related Reports
Relates :  
Description
The JVMDI function jvmdi_RedefineClasses will return an error value if any of
its argument class definitions is unacceptable to the VM. Reasons for this
correspond 1-1 with reasons for the VM rejecting class definitions passed into
ClassLoader.defineClass(). These include ClassFormatError (resp.
JVMDI_ERROR_INVALID_CLASS_FORMAT) and 
ClassCircularityError (resp. JVMDI_ERROR_CIRCULAR_CLASS_DEFINITION.  
Recently, the JVMS was revised to also throw 
UnsupportedVersionError. Consequently, we need to add
JVMDI_ERROR_UNSUPPORTED_VERTSION to reflect this. The change affects the 
documentation of jvmdi_RedefinedClasses and require the error to be defined.


gilad.bracha@eng 1998-09-24

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta FIXED IN: merlin-beta INTEGRATED IN: merlin-beta
14-06-2004

EVALUATION Will be put back when Redefinition is put back. robert.field@Eng 2000-11-20 Redefinition (see RFE 4287595) has been integrated into Merlin Beta and this was done at the same time. janet.koenig@Eng 2001-01-17
20-11-2000