On Mon, 2007-12-10 at 11:30 +0100, Korn, Christoph wrote: > I perfectly understand that loading each JSPs via a different > ClassLoader is necessary if you want to be able to reload the JSP-class, > but if the reloading-feature is turned off (development=false), I don't > see the need for a new ClassLoader for each JSP/tag. > > It's the first time I took a look into the Tomcat sources and surely > I've missed an important point, so please excuse my silly question: But > wouldn't it be possible to re-use the ClassLoader if reloading is turned > off? I attached a simple (dirty hack) patch to illustrate what I mean. > (I don't think a static map is really a good idea here, but it a first > shot to show you what I mean) > > I've already filed a bugreport for this some days ago: > http://issues.apache.org/bugzilla/show_bug.cgi?id=43878
This is a hack. This may work great for you, and that's the whole point of using OSS, but this is not a solution for others. Reloading is also (efficiently) handled by a background thread. BTW, you might want to look into the behavior when using precompilation (JSPs are mapped and loaded as servlets). Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
