Anthony, I don't know the details of the JSPs in your project, but I think it would help you to examine if there's a lot of code in them that could be moved to the application layer, also if there's a lot of plain text written directly into the JSPs that could be moved to a persistence layer as well. It will contribute towards the performance of the JSPs.
Filip, I tried your pre-compile script http://people.apache.org/~fhanik/tomcat-6-precompile.xml , on a build file that I had written which was using the old pre-compile script http://tomcat.apache.org/tomcat-4.1-doc/jasper-howto.html. As you mentioned, your script does not modify the web.xml file which is great because it eliminates the need to maintain an unmodified web.xml , which will further simplify the entire project build script. I compared the pre-compile time of my old script and your script. The total time to build my entire project (with pre-compilation included) was about 35 seconds on about 200 JSP files with both the old and the new scripts. I noticed that the jasper pre-compile step itself was quick. I have some steps in the build file that I could be eliminated now, since the web.xml doesn't get modified and this will significantly reduce the build time. I think if pre-compiling is kept separate from Tomcat's process, into a build file it works out well as it keeps things modular. It gives anyone the flexibility to choose whether one wants to pre-compile or not. Thanks a lot for providing the modified script. It worked flawlessly, I request only one change to it - if you think it's right. I would make the hostname (localhost) a variable, as it allows one to substitute a virtual host. -Regards Rashmi --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
