You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by fu...@apache.org on 2003/07/24 14:01:15 UTC
cvs commit: jakarta-tomcat-5 RELEASE-NOTES
funkman 2003/07/24 05:01:15
Modified: . RELEASE-NOTES
Log:
Removed javac leak reference
Added FAQ reference
SSI-CGI web.xml line #'s were wrong
Revision Changes Path
1.4 +30 -20 jakarta-tomcat-5/RELEASE-NOTES
Index: RELEASE-NOTES
===================================================================
RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- RELEASE-NOTES 26 Jun 2003 00:03:49 -0000 1.3
+++ RELEASE-NOTES 24 Jul 2003 12:01:14 -0000 1.4
@@ -49,15 +49,18 @@
Tomcat 5.0 Standard APIs Available:
----------------------------------
-A standard installation of Tomcat 4 makes all of the following APIs available
+A standard installation of Tomcat 5 makes all of the following APIs available
for use by web applications (by placing them in "common/lib" or "shared/lib"):
* ant.jar (Apache Ant)
* commons-collections.jar (Commons Collections)
* commons-dbcp.jar (Commons DBCP 1.0)
+* commons-el.jar (Commons Expression Language 1.0)
* commons-logging-api.jar (Commons Logging)
* commons-pool.jar (Commons Pool)
* jasper-compiler.jar (Jasper 2 Compiler)
* jasper-runtime.jar (Jasper 2 Runtime)
+* jmx.jar (From mx4j-1.1.1)
+* jmx-tools.jar (From mx4j-1.1.1)
* jsp-api.jar (JSP 2.0 API)
* commons-el.jar (JSP 2.0 Expression Language)
* naming-common.jar (JNDI Context implementation)
@@ -79,7 +82,7 @@
As described above, Tomcat 5.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 "xercesImpl.jar" file in "common/endorsed" with another
+you may replace the "xercesImpl.jar" file in "common/endorsed" with another
XML parser, as long as it is compatible with the JAXP 1.1 APIs.
@@ -89,12 +92,12 @@
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
+(ClassCastExceptions, messages indicating that the classloader
is stopped, etc.), the shared libraries state should be reinitialized.
-Something which might help is to avoid putting classes which would be
-referenced by a shared static field in the web application classloader,
-and putting them in the shared classloader instead (JARs should be put in the
+Something which might help is to avoid putting classes which would be
+referenced by a shared static field in the web application classloader,
+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).
@@ -103,8 +106,8 @@
--------------------
The Java compiler leaks memory each time a class is compiled. Web applications
-containing hundreds of JSP files may as a result trigger out of memory errors
-once a significant number of pages have been accessed. The memory can only be
+containing hundreds of JSP files may as a result trigger out of memory errors
+once a significant number of pages have been accessed. The memory can only be
freed by stopping Tomcat and then restarting it.
The JSP command line compiler (JSPC) can also be used to precompile the JSPs.
@@ -115,11 +118,11 @@
-------------------------------
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
+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. From a bash shell,
+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:
@@ -131,9 +134,9 @@
----------------------------
Having CGI and SSI available to web applications created security problems when
-using a security manager (as a malicious web application could use them to
+using a security manager (as a malicious web application could use them to
sidestep the security manager access control). In Tomcat 5.0, they have been
-disabled by default, as our goal is to provide a fully secure default
+disabled by default, as our goal is to provide a fully secure default
configuration. However, CGI and SSI remain available.
To enable CGI and SSI on Windows:
@@ -142,8 +145,8 @@
* 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
- on lines 165 and 213, as well as the associated servlet mappings
- on lines 265 and 274. Alternately, these servlet declarations and mappings can
+ on lines 226 and 250, as well as the associated servlet mappings
+ on lines 276 and 294. Alternately, these servlet declarations and mappings can
be added to your web application deployment descriptor.
To enable CGI and SSI on Unix:
@@ -152,8 +155,8 @@
* 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
- on lines 165 and 213, as well as the associated servlet mappings
- on lines 265 and 274. Alternately, these servlet declarations and mappings can
+ on lines 226 and 250, as well as the associated servlet mappings
+ on lines 276 and 294. Alternately, these servlet declarations and mappings can
be added to your web application deployment descriptor.
@@ -164,7 +167,7 @@
The URLs to be used in the policy file to grant permissions to JARs located
inside the web application repositories have changed as of Tomcat 4.1.
-In Tomcat 4.0, codeBase URLs for JARs loaded from web application
+In Tomcat 4.0, codeBase URLs for JARs loaded from web application
repositories were:
jar:file:${catalina.home}/webapps/examples/WEB-INF/lib/driver.jar!/-
@@ -176,7 +179,7 @@
Symlinking static resources:
---------------------------
-By default, 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
@@ -187,10 +190,17 @@
Enabling invoker servlet:
------------------------
-Starting with Tomcat 4.1.12, the invoker servlet is no longer available by
+Starting with Tomcat 4.1.12, the invoker servlet is no longer available by
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.
Using the invoker servlet in a production environment is not recommended and
is unsupported.
+
+
+------------------------
+When all else fails:
+------------------------
+See the FAQ
+http://jakarta.apache.org/tomcat/faq/
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org