Using non-parallel custom class loaders for Layer configurations

[Alan Bateman]

On 08/09/2016 23:29, David M. Lloyd wrote:

> Is it not necessary that any class loader in use by a Layer must be 
> parallel-capable?  Otherwise it seems like deadlocks could occur in 
> certain situations when there are references that are cyclic with 
> respect to class loaders mapped by the mapping function.
There aren't cycles in readability graph, at least not at construction 
time. They might arise later due to reflective use of addReads but that 
shouldn't change the class loader delegation graph. So I'm curious if 
you are actually running into an issue or not? I can easily come up with 
a mapping to loaders to force this but it would be unusual mapping.

BTW: I'm not opposed to exposing isParallelCapable, just curious if this 
is something that you are actually running into or not.

-Alan