craigmcc    01/08/09 22:40:43

  Modified:    catalina/src/share/org/apache/catalina Globals.java
               webapps/ROOT index.html
  Added:       .        RELEASE-NOTES-4.0-B8.txt
  Log:
  Prepare for beta-8 (if there is a need for one).
  
  Revision  Changes    Path
  1.1                  jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B8.txt
  
  Index: RELEASE-NOTES-4.0-B8.txt
  ===================================================================
                    Apache Tomcat Version 4.0 Beta 8
                    ================================
                              Release Notes
                              =============
  
  $Id: RELEASE-NOTES-4.0-B8.txt,v 1.1 2001/08/10 05:40:43 craigmcc Exp $
  
  
  ============
  INTRODUCTION:
  ============
  
  
  This document describes the changes that have been made in the current
  beta 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".
  
  This version of Tomcat 4 should be considered a "release candidate" for
  all capabilities except the mod_webapp connector.  Only bugfix changes will
  be implemented before a Tomcat 4.0 final release is made available, which
  will occur when the Servlet 2.3 and JSP 1.2 specifications go final.
  
  
  ----> UPCOMING CHANGE NOTICE:  In a future release of Tomcat 4.0, it
  ----> is likely that the default operational mode will be to run Tomcat
  ----> under a security manager (rather than the current default of not
  ----> using one).  This may necessitate editing the policy permissions
  ----> file ($CATALINA_HOME/conf/catalina.policy) if your web applications
  ----> require permissions that are not enabled by default (such as connecting
  ----> to network ports).  You are urged to test your applications with
  ----> Tomcat 4.0-b5 running under the security manager now, so that this
  ----> upcoming change will not be disruptive.  To do so, start Tomcat 4.0
  ----> with the command "$CATALINA_HOME/bin/catalina.sh start -security"
  ----> (Unix) or "%CATALINA_HOME%\bin\catalina start -security" (Windows).
  
  
  ============
  NEW FEATURES:
  ============
  
  
  --------------------
  General New Features:
  --------------------
  
  
  
  ---------------------
  Catalina New Features:
  ---------------------
  
  
  
  -------------------
  Jasper New Features:
  -------------------
  
  
  --------------------
  Webapps New Features:
  --------------------
  
  
  
  ==========================
  BUG FIXES AND IMPROVEMENTS:
  ==========================
  
  
  ------------------
  Catalina Bug Fixes:
  ------------------
  
  
  
  ----------------
  Jasper Bug Fixes:
  ----------------
  
  
  
  -----------------
  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 "$TOMCAT_HOME/jasper" directory to the "$TOMCAT_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
    "$TOMCAT_HOME/lib" directory and remove "jaxp.jar" and "crimson.jar"
    from the "$TOMCAT_HOME/jasper" directory.  It has been reported that
    Xerces 1.3.1 can be used in this fashion, but 2.x alpha releases
    can not be.
  
  * If you wish to use an XML parser (such as Xerces) in the WEB-INF/lib
    directory of your web application, this should now be possible, because
    of the modified JAXP 1.1 parser mentioned below.
  
  WARNING:  Tomcat 4.0 now ships with a modified version of the JAXP/1.1
  (Final) "jaxp.jar" and "crimson.jar" files in the "jasper" subdirectory.
  The "sealed" attribute has been removed from the manifest file for these
  two JARs, to avoid "package sealing violation" errors that were caused by
  them in a JDK 1.3 environment.  You MUST NOT replace these files with a
  different (or later) release of JAXP, unless that later release has had
  the sealed attribute removed, or you will encounter "package sealing violation"
  errors when trying to use a different XML parser in a web application.
  
  
  ---------------------
  Tomcat 4.0 and Apache:
  ---------------------
  
  The binary distribution for Tomcat 4.0 includes the most recent stable version
  of the WARP connector, which is the Tomcat component that talks to mod_webapp
  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:
  
      WebAppMount examples   warpConnection   /examples/
  
    which causes mod_webapp to automatically recognize all of your servlet
    mappings, security constraints, and other configuration elements.
  
  * 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.
  
  * 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.
  
  * There are several test failures in the "tester" unit test suite that will
    be corrected before final release.  (Most of these issues related to the
    bug that prevents BASIC authentication form operating.)
  
  
  
  1.34      +5 -5      
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java
  
  Index: Globals.java
  ===================================================================
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- Globals.java      2001/08/10 00:09:11     1.33
  +++ Globals.java      2001/08/10 05:40:43     1.34
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v 
1.33 2001/08/10 00:09:11 craigmcc Exp $
  - * $Revision: 1.33 $
  - * $Date: 2001/08/10 00:09:11 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v 
1.34 2001/08/10 05:40:43 craigmcc Exp $
  + * $Revision: 1.34 $
  + * $Date: 2001/08/10 05:40:43 $
    *
    * ====================================================================
    *
  @@ -69,7 +69,7 @@
    * Global constants that are applicable to multiple packages within Catalina.
    *
    * @author Craig R. McClanahan
  - * @version $Revision: 1.33 $ $Date: 2001/08/10 00:09:11 $
  + * @version $Revision: 1.34 $ $Date: 2001/08/10 05:40:43 $
    */
   
   public final class Globals {
  @@ -210,7 +210,7 @@
       /**
        * The descriptive information about this server and version.
        */
  -    public static final String SERVER_INFO = "Apache Tomcat/4.0-b7";
  +    public static final String SERVER_INFO = "Apache Tomcat/4.0-b8-dev";
   
   
       /**
  
  
  
  1.25      +2 -2      jakarta-tomcat-4.0/webapps/ROOT/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/ROOT/index.html,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- index.html        2001/08/10 00:09:11     1.24
  +++ index.html        2001/08/10 05:40:43     1.25
  @@ -2,7 +2,7 @@
   <html>
       <head>
       <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  -    <title>Jakarta Project - Tomcat (v4.0-b7)</title>
  +    <title>Jakarta Project - Tomcat (v4.0-b8-dev)</title>
       <style type="text/css">
         <!--
           body {
  @@ -44,7 +44,7 @@
           <td align="left" valign="top">
               <table>
                   <tr><td align="left" valign="top"><b>Tomcat</b></td></tr>
  -                <tr><td align="left" valign="top"><b>Version 4.0-b7</b></td></tr>
  +                <tr><td align="left" valign="top"><b>Version 
4.0-b8-dev</b></td></tr>
               </table>
           </td>
           <td align="right"><a href="http://jakarta.apache.org/";><img 
src="jakarta-banner.gif" height="100" width="350" border="0" alt="The Jakarta 
Project"></a></td>
  
  
  

Reply via email to