> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 11, 2001 12:18 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Jasper34: Manglers
>
>
> On Sun, 10 Jun 2001, Glenn Nielsen wrote:
>
> > Another advantage of jasper40 using a URLClassLoader for
> each individual
> > JSP page is that you don't accumulate outdated classes in
> the classloader
> > that eat up JVM memory when a JSP is recompiled. I haven't
> looked at
> > jasper33, so please let me know if that is not a problem with it.
>
> It is.
>
> On a production site it isn't a big factor - there are not too many
> reloads.
>
Depends. I've done some content publishing work where JSPs are replaced
quite often while the engine is running. Of course, there are other ways of
accomplishing the same effect, for example including HTML fragments. But it
would turn out, often enough, that we'd need to inject some code into the
text. Usually something trivial, like a link to the secure side of the same
server, or iterating over a dynamic list.
I think we'd end up with hundreds, maybe low Ks, of dead classes in memory.
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named. Any use, copying or disclosure by any other person is strictly
prohibited. If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>
