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.
The main benefit of your scheme is another one IMHO: the fact that the
name of the java and class file is predictible ( it doesn't have the
version in it ), and I am +1 to make it the default.
But I would like to keep the versioned scheme around for a while - on a
production site with many JSP files it has a smaller overhead ( no
additional class loaders - quite complex objects ). The biggest benefit
for versioned scheme is that it doesn't "mess" too much with the class
loaders - there are many hidden things and it's quite difficult to debug
and fix this kind of problems. ( especially on "special" VMs - J2ME, etc
where class loading can be quite different ).
Having both is even better :-)
( but having 4 schemes is a bit too much ).
Costin
