[EMAIL PROTECTED] wrote:
>
> Another issue:
>
> At this moment we have 4 different manglers ( == converters between
> jsp files and valid class names ):
> - original ( uses a nice .class file hack to do versioning )
> - jspc ( similar with original, but without versioning - AFAIK)
> - jasper33 ( versioning, simpler names without %xxxx, use a separate .ver
> file to avoid messing with class files )
> - jasper40 ( no versioning, uses a separate class loader per page )
>
> If nobody objects, I would like to reduce this to 2 ( 33 and 40 ). I would
> go with only 1, but each has nice advantages ( 40 has a predictible name,
> 33 avoids messing with class loaders ).
>
> If you have any reason to keep the old ones - let me know. We can add them
> later if needed ( I like the class hack, but it would take time to keep it
> updated ).
>
> Costin
I am +1 for removing the original class hack version, in its current
implementation it added alot of overhead both at compile and runtime.
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.
Regards,
Glenn
----------------------------------------------------------------------
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder |
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
----------------------------------------------------------------------
