cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt RELEASE-PLAN-4.1.txt
remm02/05/14 21:42:31 Modified:.RELEASE-NOTES-4.1.txt RELEASE-PLAN-4.1.txt Log: - Status update. Revision ChangesPath 1.5 +14 -1 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.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- RELEASE-NOTES-4.1.txt 10 May 2002 16:26:25 - 1.4 +++ RELEASE-NOTES-4.1.txt 15 May 2002 04:42:31 - 1.5 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-4.1.txt,v 1.4 2002/05/10 16:26:25 remm Exp $ +$Id: RELEASE-NOTES-4.1.txt,v 1.5 2002/05/15 04:42:31 remm Exp $ @@ -70,6 +70,10 @@ well as set default values, and add missing JNDI name field. [4.1.2] Administration Webapp: +Fix many problems defining a SSL connector through the administration +webapp. + +[4.1.2] Administration Webapp: Many cosmetic fixes. @@ -92,6 +96,10 @@ [4.1.2] DbcpDataSourceFactory: maxIdle attribute couldn't be set. +[4.1.2] Facades: +Fixed a problem where the facades would still keep a pointer to the +facaded objects after the end of the processing of the request. + Jasper Bug Fixes: @@ -107,6 +115,11 @@ [4.1.2] Generator: Fixes various problems introduced by the patch which removes the try/catch tag nesting. + +[4.1.2] #8994 +Summary: JSPs don't recompile +JspServletWrapper: +Fix JSP recompilation when the new development flag is set to true. 1.9 +4 -4 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- RELEASE-PLAN-4.1.txt 30 Apr 2002 08:41:46 - 1.8 +++ RELEASE-PLAN-4.1.txt 15 May 2002 04:42:31 - 1.9 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.1.txt,v 1.8 2002/04/30 08:41:46 remm Exp $ +$Id: RELEASE-PLAN-4.1.txt,v 1.9 2002/05/15 04:42:31 remm Exp $ Release Plan for Apache Tomcat 4.1 == @@ -20,12 +20,12 @@ * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector -* New Coyote JK2 AJP 1.4 connector +* New Coyote JK2 AJP 1.3 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements -* Enhanced manager application support for integration with development tools. +* Enhanced manager application support for integration with development tools * Custom Ant tasks to interact with the manager application directly - from build.xml scripts. + from build.xml scripts * Many other miscanellous improvements Apache Tomcat 4.1 will use the build numbering and release process first used -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt RELEASE-PLAN-4.1.txt
remm02/04/30 01:41:46
Modified:.RELEASE-PLAN-4.1.txt
Added: .RELEASE-NOTES-4.1.txt
Log:
- Change my mind again and use a common release notes document.
- Update status.
Revision ChangesPath
1.8 +1 -2 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt
Index: RELEASE-PLAN-4.1.txt
===
RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- RELEASE-PLAN-4.1.txt 25 Apr 2002 22:00:19 - 1.7
+++ RELEASE-PLAN-4.1.txt 30 Apr 2002 08:41:46 - 1.8
@@ -1,4 +1,4 @@
-$Id: RELEASE-PLAN-4.1.txt,v 1.7 2002/04/25 22:00:19 remm Exp $
+$Id: RELEASE-PLAN-4.1.txt,v 1.8 2002/04/30 08:41:46 remm Exp $
Release Plan for Apache Tomcat 4.1
==
@@ -125,7 +125,6 @@
7160 Jasper compiles files to same classname
7993 parameters in jsp:plugin for jsp Document do not work
8005 Bad Param passing with jsp:include
-8290 Problem in the code generated by jasper 2
Unconfirmed Bugs (Awaiting Reproducible Failure Case):
1.1 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
Index: RELEASE-NOTES-4.1.txt
===
Apache Tomcat Version 4.1
=
Release Notes
=
$Id: RELEASE-NOTES-4.1.txt,v 1.1 2002/04/30 08:41:46 remm Exp $
INTRODUCTION:
This document describes the changes that have been made in the current
development version of Apache Tomcat, relative to the Tomcat 4.0 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:
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:
---
[4.1.1] JspServlet, Options:
Add new reloading flag allowing to disable the JSP reloading checks,
to allow better performance on production servers.
==
BUG FIXES AND IMPROVEMENTS:
==
--
Generic Bug Fixes:
--
--
Catalina Bug Fixes:
--
[4.1.1] #8611
Summary: Sealed .jar files in WEB-INF/lib always fail to load
second class
WebappClassLoader:
The classloader will now generate codebases URL for classes loaded from
JAR file which point to the JAR, intead of using a nested jar: URL.
This change will affect security manager policy files.
Jasper Bug Fixes:
[4.1.1] #8290
Summary: Problem in the code generated by jasper 2
Generator:
This workaround for a JDK bug (BugParade Id: 4414162) introduces
a massive performance improvement when using pages containing
lots of tags.
KNOWN ISSUES IN THIS RELEASE:
* Tomcat 4.0 and JNI Based Applications
* Tomcat 4.0 Standard APIs Available
* Tomcat 4.0 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
* Jasper and Jikes
* Enabling SSI and CGI Support
* Tomcat examples web application
-
Tomcat 4.0 and JNI Based Applications:
-
Applications that require native libraries must ensure that the libraries have
been loaded prior to use. Typically, this is done with a call like:
static {
System.loadLibrary(path-to-library-file);
}
in some class. However, the application must also ensure that the library is
not loaded more than once. If the above code were placed in a class inside
the web application (i.e. under /WEB-INF/classes or /WEB-INF/lib), and the
application were reloaded, the loadLibrary() call would be attempted a second
time.
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.
--
Tomcat 4.0 Standard APIs
