tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lar...@apache.org
Subject cvs commit: jakarta-tomcat/src/doc readme
Date Sun, 11 Mar 2001 21:55:10 GMT
larryi      01/03/11 13:55:10

  Modified:    src/doc  readme
  Log:
  Changes to prepare for Milestone 2
  
  Revision  Changes    Path
  1.11      +22 -16    jakarta-tomcat/src/doc/readme
  
  Index: readme
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/src/doc/readme,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- readme	2001/02/13 04:35:01	1.10
  +++ readme	2001/03/11 21:55:09	1.11
  @@ -1,8 +1,8 @@
  -$Id: readme,v 1.10 2001/02/13 04:35:01 larryi Exp $
  +$Id: readme,v 1.11 2001/03/11 21:55:09 larryi Exp $
           
                              Release Notes for:
                              ====================
  -                           TOMCAT Version 3.3m1
  +                           TOMCAT Version 3.3m2
                              ====================
   
   
  @@ -39,32 +39,33 @@
   Kit 1.1 or later environment, including JDKs conformant with Java2.
   
   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.
  +browser at the file "tomcat_ug.html" found in the same directory as this
  +file.
   
   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
  +Tomcat 3.3m2 which are not yet covered in the accompanying documentation.
  +These changes make Tomcat 3.3m2 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
  +  Tomcat 3.3m2 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
  +  this change, web applications in Tomcat 3.3m2 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.
  +  "lib/container", "lib/common", and "lib/apps" 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
  +  (a.k.a Interceptors) available in Tomcat 3.3m2. The conf/server.xml file
     specifies which modules and connectors the Tomcat container should use along
     with their settings.
   
  @@ -86,17 +87,17 @@
     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.
  +  placed in server.xml is still supported by Tomcat 3.3m2.
   
   - 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.
  +  associated support files are not part of the binary Tomcat 3.3m2 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
  +  may be downloaded from the "v3.3-m2/apps" directory of the Tomcat 3.3m2
  +  release and placed in the "webapps" directory of your 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
  +  the Tomcat 3.3m2 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:
  @@ -104,7 +105,7 @@
   	./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:
  +  Start or restart Tomcat 3.3m2 and invoke the following URL in your browser:
   
   	http://localhost:8080/admin/test/test.jsp
   
  @@ -129,6 +130,11 @@
   	http://localhost:8080/admin/test/watchdog-jsp.jsp
   	http://localhost:8080/admin/test/watchdog-servlet.jsp
   
  +  Note: Sometimes the watchdog-jsp test will fail to list the tests that
  +  are executed.  Running the watchdog-servlet.jsp test first seems to help
  +  avoid this.  You can also restart Tomcat and re-run watchdog-jsp.jsp and
  +  the tests should be listed.
  +  
   
   =============================================================================
   3.  APPLICATION DEVELOPMENT USING TOMCAT
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, email: tomcat-dev-help@jakarta.apache.org


Mime
View raw message