-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 5.0
-
Component/s: hotspot
Jim wrote:
> I created a JDWP/JDI bug for this , but still am not quite sure
> of what is going on with unmodifiable classes. The JVMTI spec says
>
> can_redefine_any_class RedefineClasses can be called on any class
> (can_redefine_classes must also be set)
>
> ( A technically untrue defn - I can always call RedefineClasses on anything I
> want. But it might not always work.)
A more precise definition would be:
Can retransform or redefine any non-primitive non-array class.
RetransformClasses is used for retransformation and also requires
the can_retransform_classes capability.
RedefineClasses is used for redefinition and also requires
the can_redefine_classes capability.
> I created a JDWP/JDI bug for this , but still am not quite sure
> of what is going on with unmodifiable classes. The JVMTI spec says
>
> can_redefine_any_class RedefineClasses can be called on any class
> (can_redefine_classes must also be set)
>
> ( A technically untrue defn - I can always call RedefineClasses on anything I
> want. But it might not always work.)
A more precise definition would be:
Can retransform or redefine any non-primitive non-array class.
RetransformClasses is used for retransformation and also requires
the can_retransform_classes capability.
RedefineClasses is used for redefinition and also requires
the can_redefine_classes capability.
- relates to
-
JDK-8223915 JVMTI Spec: can_redefine_any_class capability spec is inconsistent
-
- Closed
-