Good point, fixing jasper servlet is a not going to help in production env ( and precompiled jsps), so it's probably not worth it.
However - I disagree that JSPs are 'just' servlets - or at least they should not be plain and stupid translation of text to 'println' servlets. The current behavior of jsps wrt memory is horrible if you have lot of content - all the plain text ends up in memory, as part of the class. It's good for cheating on benchmarks - bad for production. There are far better ways to use the memory. IMO separating the strings and loading/unloading them using a cache would help a lot in such situations ( i.e. large number of jsps == huge memory use ). Unloading not frequently/recently used jsps ( and servlets, and webapps ) might also be very nice, assuming they can handle being unloaded. But I agree that the current patch is not the right solution. Costin On 3/4/06, Remy Maucherat <[EMAIL PROTECTED]> wrote: > Costin Manolache wrote: > > But it's a separate issue - I agree that unloading unused jsps is the > > most important. > > The recommended production usage (= optimal) of JSPs is when they are > precommpiled, which means that the Jasper servlet is not used, and the > JSPs are plain servlets. Their lifecycle is then identical to the > lifecycle of servlets. > > I understand the Jasper servlet is junk, and is a testing ground for bad > ideas, though (ex: the background compilation thread, and now this). > > Rémy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
