RFR: JDK-8281001 Examine the behavior of Class::forName if the caller is null [v2]
Mandy Chung
mchung at openjdk.java.net
Wed May 25 19:47:43 UTC 2022
On Tue, 17 May 2022 20:16:48 GMT, Tim Prinzing <duke at openjdk.java.net> wrote:
>> The Class::forName behavior change to match JNI FindClass is a compatible change and seems pretty attractive as it would be expected that Class::forName would give the same behavior as FindClass which uses the system classloader. The test for 8281006 was enhanced to test for this change. Merged master to pick up fixes to unrelated test failures to reduce noise.
>
> Tim Prinzing has updated the pull request incrementally with one additional commit since the last revision:
>
> Added javadoc comment
src/java.base/share/classes/java/lang/Class.java line 361:
> 359: *
> 360: * <p>
> 361: * This method is caller sensitive. In cases where this method is called
You can drop "This method is caller sensitive." sentence for consistency with other caller-sensitive methods that do not state that explicitly. The javadoc already specifies that it uses the class loader of the current class.
-------------
PR: https://git.openjdk.java.net/jdk/pull/8711
More information about the core-libs-dev
mailing list