You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by re...@apache.org on 2001/10/07 20:02:07 UTC
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.0.1-B1.txt RELEASE-NOTES-4.0.1.txt
remm 01/10/07 11:02:06
Modified: . Tag: tomcat_40_branch RELEASE-NOTES-4.0.1-B1.txt
RELEASE-NOTES-4.0.1.txt
Log:
- Update release notes.
Revision Changes Path
No revision
No revision
1.1.2.2 +73 -19 jakarta-tomcat-4.0/Attic/RELEASE-NOTES-4.0.1-B1.txt
Index: RELEASE-NOTES-4.0.1-B1.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/Attic/RELEASE-NOTES-4.0.1-B1.txt,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- RELEASE-NOTES-4.0.1-B1.txt 2001/10/07 02:05:11 1.1.2.1
+++ RELEASE-NOTES-4.0.1-B1.txt 2001/10/07 18:02:06 1.1.2.2
@@ -1,9 +1,9 @@
- Apache Tomcat Version 4.0.1 Beta 1
- ==================================
- Release Notes
- =============
+ Apache Tomcat Version 4.0.1 Beta 1
+ ==================================
+ Release Notes
+ =============
-$Id: RELEASE-NOTES-4.0.1-B1.txt,v 1.1.2.1 2001/10/07 02:05:11 remm Exp $
+$Id: RELEASE-NOTES-4.0.1-B1.txt,v 1.1.2.2 2001/10/07 18:02:06 remm Exp $
============
@@ -34,6 +34,9 @@
General New Features:
--------------------
+ ***** Please note the revised documentation below related to *****
+ ***** using XML parsers with Tomcat 4.0 based applications. *****
+
Build process: The build process is now a lot more modular.
Xerces: Switch to the XML parser used to Xerces 1.4.3.
@@ -284,6 +287,23 @@
tests in the "jakarta-watchdog-4.0" suite.
+----------------------
+Tomcat 4.0 and AJP 1.3:
+----------------------
+
+Tomcat 4.0.1 now includes beta support for the AJP 1.3 protocol, which the
+mod_jk collection of native webserver modules implements.
+
+The AJP connector is not enabled by default. To enable it, uncomment
+the following section in $CATALINA_HOME/conf/server.xml:
+
+ <!--
+ <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
+ port="8009" minProcessors="5" maxProcessors="75"
+ acceptCount="10" debug="0"/>
+ -->
+
+
-------------------------------------
Tomcat 4.0 and JNI Based Applications:
-------------------------------------
@@ -306,19 +326,53 @@
during the lifetime of a particular JVM.
-----------------------
-Tomcat 4.0 and AJP 1.3:
-----------------------
-
-Tomcat 4.0.1 now includes beta quality support for the AJP 1.3 protocol, which
-the mod_jk collection of native webserver modules implements.
+----------------------------------
+Tomcat 4.0 Standard APIs Available:
+----------------------------------
+
+A standard installation of Tomcat 4 makes all of the following APIs available
+for use by web applications (by placing them in "common/lib" or "lib"):
+* activation.jar (Java Activation Framework)
+* jdbc2_0-stdext.jar (JDBC 2.0 Optional Package, javax.sql.*)
+* jndi.jar (JNDI 1.2 base API classes)
+* jta-spec1_0_1 (Java Transacation APIs)
+* 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)
+* xerces.jar (Xerces 1.4.3)
+
+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 the "lib" directory.
+
+
+--------------------------
+Tomcat 4.0 and XML Parsers:
+--------------------------
+
+As described above, Tomcat 4.0 makes an XML parser (and many other standard
+APIs) available to web applications. This parser is also used internally
+to parse web.xml files and the server.xml configuration file. If you wish,
+you may replace the "xerces.jar" file in "common/lib" with another XML parser,
+as long as it is compatible with the JAXP/1.1 APIs.
+
+If you wish to *not* make any XML parser visible to all web applications,
+this can be accomplished by copying the "xerces.jar" file from "common/lib"
+to both "server/lib" and "jasper", and removing it from "common/lib".
+
+
+-------------------------
+Context reloading and JCE:
+-------------------------
+
+JCE's handling of custom security providers may make context reloading fail
+with a message saying that the class loader is stopped, followed by a stack
+trace.
+The problem is that JCE attempts to use the class loader which originally
+loaded the security provider, which is the old class loader.
+
+There are two solutions to this problem. Either:
+- Move JCE and your custom security provider to the shared class loader
+- Use Security.removeProvider to remove the custom security provider on destory
-The AJP connector is not enabled by default. To enable it, please uncomment
-the following section in $CATALINA_HOME/conf/server.xml:
-
- <!--
- <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
- port="8009" minProcessors="5" maxProcessors="75"
- acceptCount="10" debug="0"/>
- -->
1.1.2.3 +54 -12 jakarta-tomcat-4.0/Attic/RELEASE-NOTES-4.0.1.txt
Index: RELEASE-NOTES-4.0.1.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/Attic/RELEASE-NOTES-4.0.1.txt,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- RELEASE-NOTES-4.0.1.txt 2001/09/28 04:46:40 1.1.2.2
+++ RELEASE-NOTES-4.0.1.txt 2001/10/07 18:02:06 1.1.2.3
@@ -3,7 +3,7 @@
Release Notes
=============
-$Id: RELEASE-NOTES-4.0.1.txt,v 1.1.2.2 2001/09/28 04:46:40 craigmcc Exp $
+$Id: RELEASE-NOTES-4.0.1.txt,v 1.1.2.3 2001/10/07 18:02:06 remm Exp $
============
@@ -92,19 +92,51 @@
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. See the documentation included
- with the connector for configuration requirements.
+ 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:
-* The version of the connector to be published with Tomcat 4.0 final has
- the following known issues:
+ WebAppDeploy examples warpConnection /examples/
- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3509
+ which causes mod_webapp to automatically recognize all of your servlet
+ mappings, security constraints, and other configuration elements.
- http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3534
+* Currently, mod_webapp forwards *all* requests under the specified
+ context path to Tomcat for processing. When Tomcat 4.0 final is released,
+ it will automatically configure itself to serve static resources
+ from Apache *unless* the resource is subject to filtering, or subject
+ to a security constraint, as defined in web.xml. No extra configuration
+ in httpd.conf will be required.
- These problems will be addressed in a future release of the connector.
+* With this release, FORM-based authentication will work correctly, but
+ there is a bug that prevents BASIC authentication from operating. This
+ will be addressed before final release.
+* If you restart Tomcat, you must also restart Apache to avoid receiving
+ "Error 400 - Bad Request" errors. This will be handled transparently
+ in the final release.
+* The combination of Apache+Tomcat currently passes all spec validation
+ tests in the "jakarta-watchdog-4.0" suite.
+
+
+----------------------
+Tomcat 4.0 and AJP 1.3:
+----------------------
+
+Tomcat 4.0.1 now includes beta support for the AJP 1.3 protocol, which the
+mod_jk collection of native webserver modules implements.
+
+The AJP connector is not enabled by default. To enable it, uncomment
+the following section in $CATALINA_HOME/conf/server.xml:
+
+ <!--
+ <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
+ port="8009" minProcessors="5" maxProcessors="75"
+ acceptCount="10" debug="0"/>
+ -->
+
+
-------------------------------------
Tomcat 4.0 and JNI Based Applications:
-------------------------------------
@@ -155,15 +187,25 @@
APIs) available to web applications. This parser is also used internally
to parse web.xml files and the server.xml configuration file. If you wish,
you may replace the "xerces.jar" file in "common/lib" with another XML parser,
-as long as it is compatible with the JAXP/1.1 APIs. Note, however, that
-problems have been observed when trying to use the "jaxp.jar" and
-"crimson.jar" files from the JAXP/1.1 Reference Implementation release
-as Tomcat's standard XML parser.
+as long as it is compatible with the JAXP/1.1 APIs.
If you wish to *not* make any XML parser visible to all web applications,
this can be accomplished by copying the "xerces.jar" file from "common/lib"
to both "server/lib" and "jasper", and removing it from "common/lib".
+-------------------------
+Context reloading and JCE:
+-------------------------
+
+JCE's handling of custom security providers may make context reloading fail
+with a message saying that the class loader is stopped, followed by a stack
+trace.
+The problem is that JCE attempts to use the class loader which originally
+loaded the security provider, which is the old class loader.
+
+There are two solutions to this problem. Either:
+- Move JCE and your custom security provider to the shared class loader
+- Use Security.removeProvider to remove the custom security provider on destory