Remy Maucherat wrote: > Costin Manolache wrote: >> The main point is to _not_ hack anything, but just use the standard. >> >> If you precompile your app - and include jasper-runtime.jar in >> WEB-INF/lib - the result should work in _any_ container - the precompiled >> jsps are _just_ regular servlets that happen to use a lib and extend from >> a base class. That used to work - I haven't tested it recently but it >> should still work. >> >> The result of precompilation must remain a webapplication that is not >> specific to tomcat ( or worse - to a specific version of tomcat, as would >> be the case here, I assume such a change won't be backported to 4.0 !). >> >> We have a standard way to declare the servlets that result from jsp >> precompile, we have a standard way to declare the mappings - and I see >> no good reason to invent another mechanism to do this. >> >> I don't like web.xml - and in 2.4 is even worse than it ever was >> ( with the XML Schema it enters a whole new level of complexity and >> uglyness). However it is good enough for this use case - and it is the >> standard. > > Hey, I think I like the longer version better. > > During deploy, we do: > - hack web.xml > - copy jasper-runtime.jar to /WEB-INF/lib > > So we can keep jasper-compiler.jar in /server/lib ?
I don't know. jasper-compiler is needed only to support development use cases, it obviously shouldn't be used on production servers. We are mixing 2 very different use cases here: - development - you don't need to precompile and jasper-compiler is neede - production - it's crazy to not precompile, and jasper-compiler serves no purpose ( and it may be safer to not have it ). A javac compiler is also not need, and probably a lot of other jars and features that are not used can be disabled. If we figure out how to .ser the web.xml and all the other descriptors - to optimize startup time - you can even run the production server without using an xml parser. IMO precompilation happens _before_ deploy - it is part of the build process, and results in a standard .war file that can be deployed in any container. The deploy stage can generate tomcat-specific files ( like .ser, expand jars from the .war, move files around or distribute them in a cluster, etc). We could have a step that precompiles and JSP - in case the original .war didn't precompile, and in this case we can generate whatever file format we want ( preferably .ser - it's much faster ). However the important case for jspc is the previous one ( i.e. precompile the app before you ship, as part of the build process ). Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
