tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: More Caching for WebappClassLoader?
Date Wed, 11 Jan 2012 19:04:58 GMT
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


Mime
View raw message