Review Request: 7193339 Prepare system classes be defined by a non-null module loader

David Holmes david.holmes at oracle.com
Fri Aug 24 15:44:36 PDT 2012


On 25/08/2012 1:53 AM, Mandy Chung wrote:
> On 8/23/2012 6:27 PM, David Holmes wrote:
>>
>> Another way to simplify this would be to add a new overload of
>> Class.forName():
>>
>> public static Class<?> forName(String name, boolean initialize)
>>
>> That way the loader argument could be dropped completely from a number
>> of the use-cases.
>
> Paul and Remi also suggest that during the jigsaw code review on the
> jigsaw-dev mailing list. It's worth considering. I plan to look at the
> usage of Class.forName in the JDK and add this new overload of
> Class.forName method if there are many use of it but I haven't got to it
> yet. I prefer to push this changeset as it and file a new CR and target
> it for JDK 8.

My other query with these changes is whether we are certain that using 
the specified loader rather than the boot loader will always be correct.

David

> Mandy


More information about the serviceability-dev mailing list