remm 2003/03/07 02:59:35 Modified: . RELEASE-NOTES-4.1.txt Log: - Status update. Revision Changes Path 1.61 +11 -37 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt Index: RELEASE-NOTES-4.1.txt =================================================================== RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt,v retrieving revision 1.60 retrieving revision 1.61 diff -u -r1.60 -r1.61 --- RELEASE-NOTES-4.1.txt 4 Mar 2003 20:35:14 -0000 1.60 +++ RELEASE-NOTES-4.1.txt 7 Mar 2003 10:59:35 -0000 1.61 @@ -1170,6 +1170,15 @@ Generator: Invalid code generated when nesting tags. +[4.1.22] TagLibraryInfoImpl: + Fix precompilation when JARs contain TLDs. + +[4.1.22] JspC: + Add package name mangling for Java keywords. + +[4.1.22] JspC: + Add documentation. + ============================ KNOWN ISSUES IN THIS RELEASE: @@ -1179,12 +1188,9 @@ * Tomcat 4.1 Standard APIs Available * Tomcat 4.1 and XML Parsers * Web application reloading and static fields in shared libraries -* JAVAC leaking memory * Linux and Sun JDK 1.2.x - 1.3.x * Enabling SSI and CGI Support * Security manager URLs -* Using Jasper 1 with Tomcat 4.1 -* Administration web application * Symlinking static resources * Enabling invoker servlet @@ -1238,7 +1244,7 @@ putting unpacked classes into a "classes" directory (not created by default), or by placing them in JAR files in the "lib" directory. -Tomcat 4.1 also makes available Xerces 2 to web applications. +Tomcat 4.1 also makes available Xerces 2.3.0 to web applications. -------------------------- @@ -1267,22 +1273,6 @@ "lib" folder, and classes should be put in the "classes" folder). --------------------- -JAVAC leaking memory: --------------------- - -The Java compiler leaks memory each time a class is compiled. Web applications -containing hundreds of JSP files may as a result trigger out of memory errors -once a significant number of pages have been accessed. The memory can only be -freed by stopping Tomcat and then restarting it. - -The JSP command line compiler (JSPC) can also be used to precompile the JSPs. - -You can prevent this by setting the JspServlet init parameter fork to true -in conf/web.xml. This tells jasper to invoke java compiles of JSP pages -as an external process. - - ------------------------------- Linux and Sun JDK 1.2.x - 1.3.x: ------------------------------- @@ -1343,22 +1333,6 @@ In Tomcat 4.1, they should be: file:${catalina.home}/webapps/examples/WEB-INF/lib/driver.jar - - ------------------------------- -Using Jasper 1 with Tomcat 4.1: ------------------------------- - -It is possible to use Jasper 1 (included in Tomcat 4.0.x) with Tomcat 4.1, as -it has the same API and supports the same JSP API. - -To use Jasper 1 instead of Jasper 2, copy the two following JARs to -$CATALINA_HOME/common/lib (overwriting the two existing JARs): -* $TOMCAT40_HOME/lib/jasper-runtime.jar -* $TOMCAT40_HOME/lib/jasper-compiler.jar - -However, users are urged to use the version of Jasper included with Tomcat 4.1 -(Jasper 2), as it has much higher performance and scalability than Jasper 1. ---------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]