remm 2003/03/12 01:49:10 Modified: webapps/docs jasper-howto.xml Log: - Docs enhancement. Revision Changes Path 1.8 +10 -43 jakarta-tomcat-catalina/webapps/docs/jasper-howto.xml Index: jasper-howto.xml =================================================================== RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/jasper-howto.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- jasper-howto.xml 7 Mar 2003 11:10:06 -0000 1.7 +++ jasper-howto.xml 12 Mar 2003 09:49:10 -0000 1.8 @@ -16,17 +16,17 @@ <section name="Table of Contents"> <p> <a href="#Introduction">Introduction</a><br /> -<a href="#Upgrading">Upgrading</a><br /> <a href="#Configuration">Configuration</a><br /> <a href="#Production Configuration">Production Configuration</a><br /> +<a href="#Web Application Compilation">Web Application Compilation</a><br /> <a href="#Using Jikes">Using Jikes</a><br /> </p> </section> <section name="Introduction"> -<p>Starting with Tomcat 4.1, Tomcat uses the Jasper 2 JSP Engine to implement -the <a href="http://java.sun.com/products/jsp/";>JavaServer Pages 1.2</a> +<p>Tomcat 5.0 uses the Jasper 2 JSP Engine to implement +the <a href="http://java.sun.com/products/jsp/";>JavaServer Pages 2.0</a> specification.</p> <p>Jasper 2 has been redesigned to significantly improve performance over @@ -56,23 +56,6 @@ </section> -<section name="Upgrading"> - -<p>Upgrading to Tomcat 4.1 and Jasper 2 from an earlier version of -Tomcat and/or Jasper.</p> - -<p>Jasper 2 generates different java source code from Jasper 1. You -must remove all previous class files generated for your JSP pages -from your <code>work</code> directory.</p> - -<p>Jasper 2 implements JSP Custom Tag Pooling. This can cause -JSP custom tags which are not compliant with the JSP specification to fail -or behave inconsistently. When upgrading from a version of Tomcat earlier -than 4.1 you should test to make sure your JSP pages which use custom tags -are working correctly.</p> - -</section> - <section name="Configuration"> <p>By default Jasper is configured for use when doing web application @@ -171,28 +154,9 @@ </section> -<section name="Production Configuration"> - -<p>When using Jasper 2 in a production Tomcat server you should consider -making the following changes from the default configuration. -<ul> -<li><strong>development</strong> - To enable background compilation of JSP -pages set this to <code>false</code>.</li> -<li><strong>fork</strong> - The internal JVM javac compiler used by Ant -has a known memory leak. And Ant requires that java compiles be synchronized, -i.e. only one JSP page can be compiled at a time. Set fork to -<code>true</code> so that Ant compiles JSP pages in a seperate JVM. -This removes the synchronization of JSP page compiles and prevents -all the javac classes from being instantiated and subsequently garbage -collected by the JVM Tomcat is running in.</li> -</ul> -</p> - -</section> - -<section name="Web application precompilation"> +<section name="Web Application Compilation"> -<p>Using Ant is the preferred way to precompile web applications. +<p>Using Ant is the preferred way to compile web applications using JSPC. Use the script given below to precompile a webapp: </p> @@ -215,7 +179,6 @@ </taskdef> <jasper2 - compile="false" validateXml="false" uriroot="${webapp.path}" webXmlFragment="${webapp.path}/WEB-INF/generated_web.xml" @@ -275,7 +238,11 @@ descriptor. Insert the <code>${webapp.path}/WEB-INF/generated_web.xml</code> at the right place inside the <code>${webapp.path}/WEB-INF/web.xml</code> file. Restart the web application (using the manager) and test it to verify it is -running fine with precompiled servlets. +running fine with precompiled servlets. An appropriate token placed in the +web application deployment descriptor may also be used to automatically +insert the generated servlet declarations and mappings using Ant filtering +capabilities. This is actually how all the webapps distributed with Tomcat +are automatically compiled as part of the build process. </p> </section>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
