Apache Tomcat Version 5.5.6 Release Notes
$ ID: Release-Notes, V 1.24 2004/09/09 16:56:59 YOAVS EXP $
============================= KNown Issues in this release: ================ ==============
* Dependency Changes * JNI Based Applications * Bundled APIs * Web application reloading and static fields in shared libraries * Tomcat on Linux * Enabling SSI and CGI Support * Security manager URLs * Symlinking static resources * Enabling invoker servlet * Viewing the Tomcat Change Log * When All else fails
=================== dependency changes: =========================== Tomcat 5.5 is Designed to Run on J2SE 5.0 And Later, And Requiresconfiguration TO Run on J2SE 1.4. make Sure to read the "running.txt" File in this Directory if you are useful j2se 1.4.
In addition, Tomcat 5.5 uses the Eclipse JDT Java compiler for compilingJSP pages. This means you no longer need to have the completeJava Development Kit (JDK) to run Tomcat, but a Java Runtime Environment (JRE) is sufficient. The Eclipse JDT Java compiler .......................
======================= jni based applations: ======================= Applications that require native libraries must ensure that the libraries havebeen loaded prior to use Typically, this is done with a call like:. static {System.loadLibrary ( "path-to-library-file");}
in some class. However, the application must also ensure that the library isnot loaded more than once. If the above code were placed in a class insidethe web application (ie under / WEB-INF / classes or / WEB-INF / lib), And the loading were reloaded, The loadLibrary () Call Would Be attempted a secondtime.
To Avoid This Problem, Place Classes That Load Native Libraries Outside of The Weweb Application, And Ensure That The LoadLibrary () Call IS Executed Only Onceduring The Lifetime of A Particular JVM.
============= bundled apis: ============= A Standard Installation of Tomcat 5.5 Makes All of Tomcat 5.5 Makes All of the Following Apis Availablefor Use by Web Applications (by Placing Them In "common / lib" or "shared / lib"): * Commons-el.jar (Commons Expression Language 1.0) * Commons-logging-api.jar (Commons Logging API 1.0.3 or Later) * Jasper-Compiler.jar (Jasper 2 Compiler) * Jasper-compiler-jdt.jar (Eclipse JDT Java Compiler) * Jasper-Runtime.jar (Jasper 2 Runtime) * JSP-API.JAR (JSP 2.0 API) * Commons-El.jar (JSP 2.0 Expression Language) * naming-common.jar (JNDI Context implementation) * naming-factory.jar (JNDI object factories for J2EE ENC support) * naming-factory-dbcp.jar (DataSource implementation based on commons-dbcp) * naming-resources .jar (JNDI DirContext implementations) * servlet-api.jar (Servlet 2.4 API) Installing the compatibility package will add the following to the list, which areneeded when running on J2SE 1.4: * jmx.jar (Java Management Extensions API 1.2 or later ) * XerceSimpl.jar (Xerces XML Parser, Version 2.6.2 or Later
You CAN Make Additional Apis Available To All of Your Web Applications BYPUTTING UNPASS INTO A "CLASSES" Directory (not created by default), or by Placing The in jar files in the "lib" directory.
To override the XML Parser Implementation or Interfaces, Use The endorsedmechanism of the jvm. The default configuration defines jars located in "common / endorsed" as endorsed.
============================================================================================================================================================================================================= ============== Web Application Reloading and static fields in shared libraries: ========================== ============================================== Some Shared Libraries (Many Are Part of the JDK) Keep references to objectsinstantiated by the web application. to avoid class loading related problems (ClassCastExceptions, messages indicating that the classloaderis stopped, etc.), the shared libraries state should be reinitialized.Something which might help is to avoid putting classes which would bereferenced 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).
================ Tomcat on Linux: ======================== Glibc 2.2 / Linux 2.4 Users sales surplend AN Environment Variable: Export ld_assume_kernel = 2.2.5
Redhat Linux 9.0 Users Should Use The Following Setting To AvoidStability Problems: Export Ld_assume_kernel = 2.4.1
============================= Enabling SSI and CGI Support: ================ ============== Because of the security risks associated with CGI and SSI availableto web applications, these features are disabled by default.To enable and configure CGI support, please see the cgi-howto.html Page.
To Enable and Configue SSI Support, please see the ssi-howto.html page.
====================== Security Manager urls: ============================= in Order To grant security permissions to jars located inside the flollion formatin your policy file:
File: $ {catalina.home} /webapps/examples/web-inf/lib/driver.jar
============================ Symlinking static resources: ============================================================================================================================================================================================================= ========== by default, UNIX SYMLINKS WILL NOT WORK WHEN USED IN A Web Application To LinkResources Located Outside The Web Application Root Directory.
This Behavior Is Optional, and The "allowlinking" Flag May Be used to disablethe check.
========================= Enabling invoker servlet: ============================================ ==== Starting with Tomcat 4.1.12, the invoker servlet is no longer available bydefault in all webapps. Enabling it for all webapps is possible by editing $ CATALINA_HOME / conf / web.xml to uncomment the "/ servlet / *" servlet -mappingdefinition.Using the invoker servlet in a production environment is not recommended andis unsupported More details are available on the Tomcat FAQ athttp:. //jakarta.apache.org/tomcat/faq/misc.html#invoker.
============================== viewing the tomcat change log: =============== ================= See Changelog.html in this Directory.
==================== when all else fails: ============================ See the faqttp: / /JAKARTA.APache.org/tomcat/faq/
