You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by yo...@apache.org on 2003/06/26 02:03:49 UTC

cvs commit: jakarta-tomcat-5 RELEASE-NOTES

yoavs       2003/06/25 17:03:49

  Modified:    .        RELEASE-NOTES
  Log:
  Fixed bug 19939
  
  Revision  Changes    Path
  1.3       +17 -17    jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- RELEASE-NOTES	4 Feb 2003 23:41:01 -0000	1.2
  +++ RELEASE-NOTES	26 Jun 2003 00:03:49 -0000	1.3
  @@ -69,7 +69,7 @@
   putting unpacked classes into a "classes" directory (not created by default),
   or by placing them in JAR files in the "lib" directory.
   
  -Tomcat 5.0 also makes available Xerces 2 to web applications.
  +Tomcat 5.0 also makes Xerces 2 available to web applications.
   
   
   --------------------------
  @@ -90,11 +90,11 @@
   Some shared libraries (many are part of the JDK) keep references to objects
   instantiated by the web application. To avoid class loading related problems
   (ClassCastExceptions, messages indicating that the classloader 
  -is stopped, ...), the shared libraries state should be reinitialized.
  +is stopped, etc.), the shared libraries state should be reinitialized.
   
  -Something which could help is to avoid putting classes which would be 
  +Something which might help is to avoid putting classes which would be 
   referenced by a shared static field in the web application classloader, 
  -and put them in the shared classloader instead (the JARs should be put in the 
  +and putting them in the shared classloader instead (JARs should be put in the 
   "lib" folder, and classes should be put in the "classes" folder).
   
   
  @@ -114,13 +114,13 @@
   Linux and Sun JDK 1.2.x - 1.3.x:
   -------------------------------
   
  -Virtual machine crashes can be experienced when using certain combinations of
  +Virtual machine crashes may be experienced when using certain combinations of
   kernel / glibc under Linux with Sun Hotspot 1.2 to 1.3. The crashes were 
   reported to occur mostly on startup. Sun JDK 1.4 does not exhibit the problems,
   and neither does IBM JDK for Linux.
   
  -The problems can be fixed by reducing the default stack size. At bash shell, 
  -do "ulimit -s 2048"; use "limit stacksize 2048" for tcsh.
  +The problems can be fixed by reducing the default stack size. From a bash shell, 
  +use "ulimit -s 2048"; use "limit stacksize 2048" for tcsh.
   
   GLIBC 2.2 / Linux 2.4 users should also define an environment variable:
   export LD_ASSUME_KERNEL=2.2.5
  @@ -136,24 +136,24 @@
   disabled by default, as our goal is to provide a fully secure default 
   configuration. However, CGI and SSI remain available.
   
  -On Windows:
  +To enable CGI and SSI on Windows:
   * rename the file %CATALINA_HOME%\server\lib\servlets-cgi.renametojar to
     %CATALINA_HOME%\server\lib\servlets-cgi.jar.
   * rename the file %CATALINA_HOME%\server\lib\servlets-ssi.renametojar to
     %CATALINA_HOME%\server\lib\servlets-ssi.jar.
   * in %CATALINA_HOME%\conf\web.xml, uncomment the servlet declarations starting
  -  line 165 and 213, as well as the associated servlet mappings 
  -  line 265 and 274. Alternately, these servlet declarations and mappings can
  +  on lines 165 and 213, as well as the associated servlet mappings 
  +  on lines 265 and 274. Alternately, these servlet declarations and mappings can
     be added to your web application deployment descriptor.
   
  -On Unix:
  +To enable CGI and SSI on Unix:
   * rename the file $CATALINA_HOME/server/lib/servlets-cgi.renametojar to
     $CATALINA_HOME/server/lib/servlets-cgi.jar.
   * rename the file $CATALINA_HOME/server/lib/servlets-ssi.renametojar to
     $CATALINA_HOME/server/lib/servlets-ssi.jar.
   * in $CATALINA_HOME/conf/web.xml, uncomment the servlet declarations starting
  -  line 165 and 213, as well as the associated servlet mappings 
  -  line 265 and 274. Alternately, these servlet declarations and mappings can
  +  on lines 165 and 213, as well as the associated servlet mappings 
  +  on lines 265 and 274. Alternately, these servlet declarations and mappings can
     be added to your web application deployment descriptor.
   
   
  @@ -162,7 +162,7 @@
   ---------------------
   
   The URLs to be used in the policy file to grant permissions to JARs located
  -inside the web application repositories have changed in Tomcat 5.0.
  +inside the web application repositories have changed as of Tomcat 4.1.
   
   In Tomcat 4.0, codeBase URLs for JARs loaded from web application 
   repositories were:
  @@ -176,7 +176,7 @@
   Symlinking static resources:
   ---------------------------
   
  -Unix symlinks will not work when used in a web application to link resources 
  +By default, Unix symlinks will not work when used in a web application to link resources 
   located outside the web application root directory.
   
   This behavior is optional, and the "allowLinking" flag may be used to disable
  @@ -188,7 +188,7 @@
   ------------------------
   
   Starting with Tomcat 4.1.12, the invoker servlet is no longer available by 
  -default in all webapp. Enabling it for all webapps is possible by editing
  +default in all webapps. Enabling it for all webapps is possible by editing
   $CATALINA_HOME/conf/web.xml to uncomment the "/servlet/*" servlet-mapping
   definition.
   
  
  
  

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