cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.0.txt
ccain 01/09/16 23:29:24 Modified:.RELEASE-NOTES-4.0.txt Log: Add the new Ant version dependancy (1.4) to the release notes. Revision ChangesPath 1.4 +4 -2 jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt Index: RELEASE-NOTES-4.0.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- RELEASE-NOTES-4.0.txt 2001/09/16 05:59:42 1.3 +++ RELEASE-NOTES-4.0.txt 2001/09/17 06:29:24 1.4 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-4.0.txt,v 1.3 2001/09/16 05:59:42 craigmcc Exp $ +$Id: RELEASE-NOTES-4.0.txt,v 1.4 2001/09/17 06:29:24 ccain Exp $ @@ -32,11 +32,13 @@ General New Features: +The 1.4 release of Ant is now required in order to build Tomcat 4.0 +from source. Previous versions relied on Ant 1.3. + - Catalina New Features: - - ---
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.0.txt
craigmcc01/09/17 11:38:48 Modified:.RELEASE-NOTES-4.0.txt Log: Update release notes to reflect latest bug fixes, and the current state of the web connector. I'm currently investigating 3529 and 3640, which might modify the known issue section about JSPC - other than that (and any more bugfixes for reports not yet submitted), this is what I plan to publish tonight with the final release. Revision ChangesPath 1.5 +36 -16jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt Index: RELEASE-NOTES-4.0.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- RELEASE-NOTES-4.0.txt 2001/09/17 06:29:24 1.4 +++ RELEASE-NOTES-4.0.txt 2001/09/17 18:38:48 1.5 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-4.0.txt,v 1.4 2001/09/17 06:29:24 ccain Exp $ +$Id: RELEASE-NOTES-4.0.txt,v 1.5 2001/09/17 18:38:48 craigmcc Exp $ @@ -13,6 +13,8 @@ This document describes the changes that have been made in the current release candidate release of Apache Tomcat, relative to the previous release. +The release notes for all prior releases of Tomcat 4.0 are also included, for +your reference. Bug reports should be entered at the bug reporting system for Jakarta projects at: @@ -33,7 +35,20 @@ The 1.4 release of Ant is now required in order to build Tomcat 4.0 -from source. Previous versions relied on Ant 1.3. +from source. Previous versions relied on Ant 1.3. Please read the +BUILDING.txt file in the top-level directory of the source distribution +for more information about building Tomcat 4.0 from source. + +Tomcat 4.0 now makes an XML parser, as well as other API classes, available +to web applications by default. This behavior is consistent with that of +previous versions of Tomcat, and will make porting apps much less painful. +See Tomcat 4.0 Standard APIs Available, below, for more information. + +The build.xml example file included in the Application Developer's Guide now +creates a compilation classpath that automatically includes all of the classes +that Tomcat 4.0 exposes to web applications. You should not need to customize +this file unless you need to add additional application-specific classes into +/WEB-INF/lib. - @@ -98,7 +113,12 @@ Webapps Bug Fixes: - +The form-based login example will now operate correctly even if cookies are +turned off. Note that this is an extension to the servlet specification's +requirements, which only require form-based login to work if either cookies +or SSL sessions are used to maintain session identity. + KNOWN ISSUES IN THIS RELEASE: @@ -113,22 +133,18 @@ inside Apache 1.3. The current state of this support is summarized as follows: * The mod_webapp connector is configured based on the contents of the - web.xml file for your web application. The only required per-webapp - configuration information in your Apache 1.3 httpd.conf file is - something like this: - -WebAppDeploy examples warpConnection /examples/ - - which causes mod_webapp to automatically recognize all of your servlet - mappings, security constraints, and other configuration elements. - -* The final version of the mod_webapp connector will be released separately - when remaining bugs are fixed. If any changes are necessary to the Java - end of the connector, they will be packaged in a single JAR file (warp.jar) - to be installed into $CATALINA_HOME/server/lib of the Tomcat 4.0 final - release. + web.xml file for your web application. See the documentation included + with the connector for configuration requirements. + +* The version of the connector to be published with Tomcat 4.0 final has had + all outstanding bugs fixed for Unix platforms. However, a known issue + remains with the connector on Windows platforms. For more information, see + +http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3509 + This problem will be addressed in a future release of the connector. + - Tomcat 4.0 and JNI Based Applications: - @@ -179,6 +195,10 @@ * mail.jar (JavaMail 1.2) * servlet.jar (Servlet 2.3 and JSP 1.2 APIs) * tyrex-0.9.7.0.jar (Tyrex XA-compatible data source from tyrex.exolab.org) + +You can make additional APIs available to all of your web applications by +putting unpacked classes into a classes directory (not created by default), +or by placing them in JAR files in
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.0.txt RELEASE-PLAN-4.0.txt
craigmcc01/09/17 18:09:37 Modified:.RELEASE-NOTES-4.0.txt RELEASE-PLAN-4.0.txt Log: Update to final status for release. Revision ChangesPath 1.6 +12 -17jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt Index: RELEASE-NOTES-4.0.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- RELEASE-NOTES-4.0.txt 2001/09/17 18:38:48 1.5 +++ RELEASE-NOTES-4.0.txt 2001/09/18 01:09:37 1.6 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-4.0.txt,v 1.5 2001/09/17 18:38:48 craigmcc Exp $ +$Id: RELEASE-NOTES-4.0.txt,v 1.6 2001/09/18 01:09:37 craigmcc Exp $ @@ -108,7 +108,13 @@ Compiler: Remove a spurious null in an error message when no mapping back to the original source file can be performed. +JspC: Fix bugs that made it impossible to precompile JSP pages that referenced +custom tag libraries with the jspc command line tool. +Compiler: If the user specifies a name attribute on the jsp:plugin tag, +carry this through to the generated embed and object tags. + + - Webapps Bug Fixes: - @@ -136,13 +142,14 @@ web.xml file for your web application. See the documentation included with the connector for configuration requirements. -* The version of the connector to be published with Tomcat 4.0 final has had - all outstanding bugs fixed for Unix platforms. However, a known issue - remains with the connector on Windows platforms. For more information, see +* The version of the connector to be published with Tomcat 4.0 final has + the following known issues: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3509 + +http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3534 - This problem will be addressed in a future release of the connector. + These problems will be addressed in a future release of the connector. - @@ -165,18 +172,6 @@ To avoid this problem, place classes that load native libraries outside of the web application, and ensure that the loadLibrary() call is executed only once during the lifetime of a particular JVM. - - -- -JSP Command Line Compiles: -- - -Tomcat 4.0 includes a command-line utility (jspc.bat or jscp.sh) to precompile -individual JSP pages, or all JSP pages in an application. If the page(s) you -are compiling include references to custom tag libraries, you MUST use the --webapp command line option so that the entire web application (including -all the required tag library descriptors and JAR files) is available to the -compiler. -- 1.23 +5 -11 jakarta-tomcat-4.0/RELEASE-PLAN-4.0.txt Index: RELEASE-PLAN-4.0.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.0.txt,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- RELEASE-PLAN-4.0.txt 2001/09/17 18:00:53 1.22 +++ RELEASE-PLAN-4.0.txt 2001/09/18 01:09:37 1.23 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.0.txt,v 1.22 2001/09/17 18:00:53 craigmcc Exp $ +$Id: RELEASE-PLAN-4.0.txt,v 1.23 2001/09/18 01:09:37 craigmcc Exp $ Release Plan for Apache Tomcat 4.0 == @@ -48,25 +48,19 @@ Connectors 3509Apache 1.3.20 and mod_webapp and Tomcat 4b7 HANGS (likely to be the same issue as 1788) +(WILL BE NOTED AS AN ISSUE ON THE RELEASE NOTES) -Connectors 3534File Upload doesn't work with Apache, mod_webapp, Tomcat 4 +Connectors 3534File Upload doesn't work with Apache, mod_webapp, Tomcat 4, +and WebDAV. (WILL BE NOTED AS AN ISSUE ON THE RELEASE +NOTES) Nice To Have Fixes Before Final Release: --- -Jasper 3055jsp:plugin tag ignores the name attribute -Servletapi 3196Javadoc errors during build - -Servletapi 3344Typo in javadocs - - Unconfirmed Bugs (Awaiting Reproducible Failure Case): - - -Jasper 3529JSPC cannot handle tag libraries (reopened) -(under investigation) Jasper 3640Fix for JSPC handling of tag libraries in a JAR (probably related to 3529)
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.0.txt RELEASE-PLAN-4.0.txt
craigmcc01/09/15 11:17:44 Modified:.RELEASE-PLAN-4.0.txt Added: .RELEASE-NOTES-4.0.txt Log: Update release plan to current status (last two must address bugs other than those in the connector), and post the initial version of what will be the release notes for 4.0 final. Revision ChangesPath 1.19 +5 -1 jakarta-tomcat-4.0/RELEASE-PLAN-4.0.txt Index: RELEASE-PLAN-4.0.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.0.txt,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- RELEASE-PLAN-4.0.txt 2001/09/15 01:18:10 1.18 +++ RELEASE-PLAN-4.0.txt 2001/09/15 18:17:44 1.19 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.0.txt,v 1.18 2001/09/15 01:18:10 craigmcc Exp $ +$Id: RELEASE-PLAN-4.0.txt,v 1.19 2001/09/15 18:17:44 craigmcc Exp $ Release Plan for Apache Tomcat 4.0 == @@ -46,6 +46,8 @@ Bugs That Must Be Addressed Before Final Release: +Catalina3614Bug in manager webapp + Connectors 2997Webapp connector should recover when Tomcat is restarted Connectors 3476Cannot use other than default context when using mod_webapp @@ -54,6 +56,8 @@ (likely to be the same issue as 1788) Connectors 3534File Upload doesn't work with Apache, mod_webapp, Tomcat 4 + +Jasper 3617null in JasperException Nice To Have Fixes Before Final Release: 1.1 jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt Index: RELEASE-NOTES-4.0.txt === Apache Tomcat Version 4.0 = Release Notes = $Id: RELEASE-NOTES-4.0.txt,v 1.1 2001/09/15 18:17:44 craigmcc Exp $ INTRODUCTION: This document describes the changes that have been made in the current release candidate release of Apache Tomcat, relative to the previous release. Bug reports should be entered at the bug reporting system for Jakarta projects at: http://nagoya.apache.org/bugzilla/ Please report bugs and feature requests under product name Tomcat 4. NEW FEATURES: General New Features: - Catalina New Features: - --- Jasper New Features: --- Webapps New Features: == BUG FIXES AND IMPROVEMENTS: == -- Generic Bug Fixes: -- -- Catalina Bug Fixes: -- WebdavServlet: The protocol name is no longer hard coded when parsing a destination header, which fixes problems when using https. StandardManager: Catch and log exceptions thrown by session.expire() when sessions are being timed out. Previously, any such exception would terminate the thread that checks for timed out sessions. StandardWrapperValve: Do not set a character encoding on the default page created for an HTTP status code. This was causing problems for Netscape Navigator when handling 302 redirects. Jasper Bug Fixes: Parser: Fix a bug that was causing null pointer exceptions in JakartaCommentGenerator. - Webapps Bug Fixes: - KNOWN ISSUES IN THIS RELEASE: -- Tomcat 4.0 and XML Parsers: -- Previous versions of Tomcat 4.0 exposed the XML parser used by Jasper (the JAXP/1.1 reference implementation) to web applications. This is no longer the case, because Jasper loads its parser with a new class loader instead. Keep the following points in mind when considering how to use XML parsers in Tomcat 4.0 and your web applications: * If you wish to make the JAXP/1.1 RI XML parser available to all web applications, simply move the jaxp.jar and crimson.jar files from the $CATALINA_HOME/jasper directory to the $CATALINA_HOME/lib directory. * If you wish to make another XML parser that is JAXP/1.1-compatible available to all web applications, install that parser into the $CATALINA_HOME/lib directory and remove jaxp.jar and crimson.jar from the $CATALINA_HOME/jasper directory. It has been reported that Xerces 1.3.1 can be used in this fashion,
