RFC: 8223915: JVMTI Spec: can_redefine_any_class capability spec is inconsistent
Alan Bateman
Alan.Bateman at oracle.com
Wed May 15 07:27:46 UTC 2019
On 14/05/2019 21:20, serguei.spitsyn at oracle.com wrote:
> :
>
> Summary:
>
> The spec of the "can_redefine_any_class" needs to be more clear and
> consistent.
> The suggestion is to change the "can_redefine_any_class" capability spec|
> from:||
> "Can modify (retransform or redefine) any modifiable class. See
> IsModifiableClass." |||
> |to: "Can redefine any modifiable class. See IsModifiableClass.
> (can_redefine_classes must also be set)" |
Can you summarize how this capability is used? At some point we may have
modules that cannot be redefined so IsModifableClass has to return false
(via its parameter) for classes in that module. The wording for the
capability in that function seems to conflict.
-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20190515/31626837/attachment.html>
More information about the serviceability-dev
mailing list