Remy Maucherat wrote:
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 ).
Ok, so the deployer shouldn't do anything in addition to what it does right now, then ?
That's fine by me, it works good enough, and I've documented how to use the Ant script :)
I think I should add copying jasper-runtime.jar to /WEB-INF/lib, then.
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
