Konstantin, On 1/10/12 9:16 PM, Konstantin Kolinko wrote: > I think that instead of caching the class instance itself it would be > safe to cache the fact that the class was loaded from the parent > classloader. It separates responsibilities and solves the issue with > dynamic classloading. The difference is small though. > Actually WebappClassLoader#notFoundResources already serves similar purpose.
I like this idea: it certainly improves the situation, though it will still reduce some flexibility because if the class (or other resource) appears in a /different/ location at some point, that new resource won't be found. It might make patch-style dynamic class loading difficult. -chris
signature.asc
Description: OpenPGP digital signature
