Rashmi Rubdi wrote:
On 5/29/07, Berglas, Anthony <[EMAIL PROTECTED]> wrote:
Thanks for that, but I don't see how it will help. If you look below
it is the jasper2 that is causing me grief, which is essentially the
same as yours.
How long does it take to precompile the JSPs. Is it several JSPs per
second or several seconds per JSP? My JSPs take over 20 seconds to
compile interactively, which would make precompiling all of them
infeasible except for a nightly build.
Pre-compiling JSPs does take a while because, first JSPs are converted
to .java files , then the .java files are compiled to .class files,
and then the web.xml is modified.
mine go pretty fast, for tc6 it only does two steps, .jsp -> .java -> .class
the whole process is over before I know it.
Most people reserve pre-compiling JSPs to just before the app is ready
for deployment into production environment. Pre-compiling for
development, staging and other environments would take too much time
and effort unnecessarily.
I'm surprised that your script needs those package rename hacks. Feels
like precompiling into Tomcat's work area should be built in,
bin/precompileJsps.bat|.sh.
you'd understand if you were using TC4, were all JSPs had the package
name org.apache.jsp, regardless of their location.
you're also missing the point of my script, normal "precompile" you turn
everything into static servlets, with mapping inside web.xml
with my script, you are precompiling, yet you are keeping the ability to
modify your .jsp files at runtime
Filip
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
