tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dmk...@earthlink.net (David M. Karr)
Subject Re: JSPC Precompiling Issues and a handy utility
Date Thu, 01 Aug 2002 19:47:56 GMT
>>>>> "Rick" == Rick Fincher <rnf@tbird.com> writes:

    Rick> Hi All,
    Rick> There has been some discussion on here and on the TAGLIBS list about
    Rick> precompiling JSP's in Tomcat.

    Rick> To avoid confusion, before I go on I want to point out that there has been a
    Rick> change in Tomcat 4.1.8 in the naming conventions of servlets generated from
    Rick> JSP's.

    Rick> In 4.1.8 a JSP file CATALINA_HOME/webapps/myApp/main.jsp gets compiled into
    Rick> a servlet  CATALINA_HOME/work/Standalone/localhost/myApp/main_jsp.java.

    Rick> Prior to 4.1.8 the servlet created was called main$jsp.java.  So they
    Rick> changed the name convention from $jsp.java to _jsp.java.

    Rick> I'll use the 4.1.8 names in this post.

    Rick> Anyway, when I use jspc to precompile I get all the .java files in  , but no
    Rick> class files.  Does jspc only generate the servlet java files?  The whole
    Rick> point of precompiling was to prevent javac from being called to compile
    Rick> those servlets to work around the javac memory leak and speed up page
    Rick> loading.

The Tomcat JspC process only generates the servlet code.  You have to compile
the code yourself.  It's easy enough to set that up as part of your build
process.

-- 
===================================================================
David M. Karr          ; Java/J2EE/XML/Unix/C++
dmkarr@earthlink.net


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message