> > Demanding that only one version of B can exist will pretty much keep me > and a lot of other people from caring about or contributing to what might > happen with this JSR. >
I think the trick is to provide a non-hacky way that someone can plug something that can create a hierarchy of classloaders using whatever hierachy it chooses (and yes, that has some implications for that thing's load-order and privilege), without forcing that down the throats of all applications, since such things add overhead and complexity that not everything needs. I think there's a spectrum from "prove it works" to "pray it works" with a lot of stops in-between that different kinds of applications have tolerance for (I once was hired to untangle a huge application used in some very scary places, which was routinely built and deployed with an additional ancient version of itself on the classpath because the sources to some classes had been lost and nobody there understood what they did), and different trade-offs along the way. Are you looking for the JSR to solve the problem, or just to make it straightforward to layer a solution on top of it? -Tim
