score:1

it was the one thing i imagined. i should have tested. the classloader c lives in a chain of classloaders, x could be found in the parent classloader p, while y could only be found in c. since x was loaded via p, it looked for y in p, didn't find it, hence the exception.


Related Query

More Query from same tag