If that is the only reason the jdk is needed couldn't we start
precompiling
the jsps in the war to save people needing a full install?
Well, we definitely can't do it for the war, since I think different
servlet containers do things differently.
It's up for debate if you could do it with a single servlet container,
or if different versions of java compile the jsps differently. I
looked in to precompilation a long while ago, and found it to be a big
bitch. If anyone wants to look in to doing it, and testing against
sun's 1.4 and 1.5 jre's, as well as a few of the other jre's, then I
think we'd be happy to roll it in.
If that is the only reason the jdk is needed couldn't we start
precompiling
the jsps in the war to save people needing a full install?
Well, we definitely can't do it for the war, since I think different
servlet containers do things differently.
This is true, we did try making a ready to go release for resin at one point. The solution we have in place is apparently common for low volume websites. Although often it is an external applicaiton that you run, that requests pages forcing them to be compiled.
It's up for debate if you could do it with a single servlet container,
or if different versions of java compile the jsps differently. I
looked in to precompilation a long while ago, and found it to be a big
bitch. If anyone wants to look in to doing it, and testing against
sun's 1.4 and 1.5 jre's, as well as a few of the other jre's, then I
think we'd be happy to roll it in.
The different JDKs are okay, it is the servlet containers that are a problem.
To wit GeoServer is not working in the Oracle servelet containers, because some of our variable names are "reservered" when the JSPs are compiled in that environment (as I recall "label" is in conflict").