Re: Revisiting JDK-8161269

2016-09-16 Thread Alan Bateman
On 16/09/2016 08:36, David M. Lloyd wrote: OK. For this issue though, would it not make sense to look at the null parent class loader case in a specific and separate way: in the past, such class loaders had access to all platform classes, so as a compatibility factor it would not be unreaso

Re: Revisiting JDK-8161269

2016-09-16 Thread David M. Lloyd
On 09/16/2016 10:30 AM, Alan Bateman wrote: On 16/09/2016 07:21, David M. Lloyd wrote: Hi Alan, In JDK-8161269 you said [1] that the "null" class loader has never been specified to contain all Java SE types, using this as a justification to reject this issue as "Not an Issue", regardless of th

Re: Revisiting JDK-8161269

2016-09-16 Thread Alan Bateman
On 16/09/2016 07:21, David M. Lloyd wrote: Hi Alan, In JDK-8161269 you said [1] that the "null" class loader has never been specified to contain all Java SE types, using this as a justification to reject this issue as "Not an Issue", regardless of the compatibility impact (particularly the c