larryi 01/02/12 20:35:02
Modified: src/doc readme
Log:
Update to document some major changes from Tomcat 3.2
Revision Changes Path
1.10 +88 -1 jakarta-tomcat/src/doc/readme
Index: readme
===================================================================
RCS file: /home/cvs/jakarta-tomcat/src/doc/readme,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- readme 2001/02/08 21:38:31 1.9
+++ readme 2001/02/13 04:35:01 1.10
@@ -1,4 +1,4 @@
-$Id: readme,v 1.9 2001/02/08 21:38:31 larryi Exp $
+$Id: readme,v 1.10 2001/02/13 04:35:01 larryi Exp $
Release Notes for:
====================
@@ -41,6 +41,93 @@
For detailed information about installing and running Tomcat, point your
browser at file "doc/tomcat_ug.html" under the directory into which
you unpacked the Tomcat distribution.
+
+IMPORTANT NOTE: Some important changes have been recently added to
+Tomcat 3.3m1 which are not yet covered in the accompanying documentation.
+These changes make Tomcat 3.3m1 quite different from Tomcat 3.2 in a number
+of ways. These changes include the following:
+
+- Class Loading:
+
+ Tomcat 3.3m1 now uses a new hierarchy of class loaders. It provides for the
+ separation of the classes used by the Tomcat container and the classes used
+ by web applications. This solves a major problem in Tomcat 3.2 where all
+ web applications had to share Tomcat's XML parser. Now each web applicaton
+ can have its own XML parser, or if desired all web applications can share
+ an XML parser different from the one used by Tomcat. As a side effect of
+ this change, web applications in Tomcat 3.3m1 are not provided an XML
+ parser by default. You must supply one if your web application requires
+ one. For details about where to place jar files, see the README files in the
+ "lib", "lib/common", and "lib/shared" directories of your Tomcat installation.
+
+- Tomcat Configuration:
+
+ The configuration of Tomcat has been reorganized into separate configuration
+ files. The conf/modules.xml file contains module definitions for the modules
+ (a.k.a Interceptors) available in Tomcat 3.3m1. The conf/server.xml file
+ specifies which modules and connectors the Tomcat container should use along
+ with their settings.
+
+ Web application configuration can now be specified in a conf/apps.xml file or
+ in separate flies using the name conf/apps-[name].xml. For example,
+ conf/apps-examples.xml would be the configuration file for the examples web
+ application.
+
+ The tomcat.policy file remains in the "conf" directory. However, other
+ configuration files have been moved to directories under "conf".
+
+ Another change related to Tomcat configuration is that auto-generated
+ web server configuration files, such as tomcat-apache.conf, are not generated
+ by default. To turn these on, add the following modules after the
+ <AutoWebApp ... /> module in the server.xml file:
+
+ Apache configs: <ApacheConfig />
+ IIS config: <IISConfig />
+ Netscape config: <NSConfig />
+
+ Note: The old organization used in Tomcat 3.2 where all the configuration is
+ placed in server.xml is still supported by Tomcat 3.3m1.
+
+- Tomcat Testing:
+
+ The "test" web application along with the test-tomcat.xml and
+ associated support files are not part of the binary Tomcat 3.3m1 distribution.
+ The "test" web application is supplied separately as "test.war". This file
+ may be downloaded from the "v3.3-m1/apps" directory of the Tomcat 3.3m1
+ release and placed in the "webapps" directory of you installation. Running
+ the test has been integrated into the Admin web application that is part of
+ the Tomcat 3.3m1 distribution. A preliminary step to running the test is to
+ "trust" the Admin web application. It is set to "untrusted" by default. This
+ change can be accomplished by executing the command from the TOMCAT_HOME
+ directory with JAVA_HOME set:
+
+ ./bin/tomcat.sh run -enableAdmin <-- Unix
+ bin\tomcat run -enableAdmin <-- Windows
+
+ Start or restart Tomcat 3.3m1 and invoke the following URL in your browser:
+
+ http://localhost:8080/admin/test/test.jsp
+
+ and then click "Submit Query". The build targets for the Ant based test
+ script are then listed and the tests executed. After the tests are
+ completed, the results will appear with "FAILED Tests" listed first,
+ followed the "PASSED Tests".
+
+ For security reasons, after you are done with the test, you should either
+ restore the Admin web application to the default "untrusted" state, or change
+ the password for the "admin" user. To restore the Admin web application to
+ the default "untrusted" state, change trusted="true" to trusted="false" in
+ the "apps-admin.xml" file found in Tomcat's "conf" directory. If you want to
+ leave the Admin web application as "trusted, you should change the password
+ for the "admin" user in the "admin-users.xml" file located in Tomcat's
+ "conf/users" directory.
+
+ You may also download the Watchdog jsp-tests.war and servlet-tests.war web
+ applications to your "webapps" directory. These tests may be run in the
+ same fashion as the "test" web application using the following URLs:
+
+ http://localhost:8080/admin/test/watchdog-jsp.jsp
+ http://localhost:8080/admin/test/watchdog-servlet.jsp
=============================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
