RFR: 8349145: Make Class.getProtectionDomain() non-native [v4]
Alan Bateman
alanb at openjdk.org
Tue Feb 4 16:40:10 UTC 2025
On Tue, 4 Feb 2025 14:59:46 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:
>> There may need to be some follow-on cleanup, e.g. I'm wondering if Lookup.cachedProtectionDomain is needed now.
>
> One of the reasons I wanted to move this out of Hotspot as a native call is that it might make further work with ProtectionDomain easier to do all in Java, except there's still a bit of coupling in the JVM with the name of the class and that it's passed through defineClass (resolve_from_stream) and initialized in the mirror. So I guess that's still a lot.
Aside from JVMTI (CFLH for example), is there anything left in the VM that needs this? The last param to JVM_DefineClassWithSource has the location from the code source if available.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/23396#discussion_r1941523958
More information about the core-libs-dev
mailing list