cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2005-07-22 Thread yoavs
yoavs   2005/07/22 06:07:52

  Modified:.RELEASE-NOTES
  Log:
  Bugzilla 33739: http://issues.apache.org/bugzilla/show_bug.cgi?id=33739
  
  Revision  ChangesPath
  1.26  +2 -2  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- RELEASE-NOTES 19 Jan 2005 20:30:26 -  1.25
  +++ RELEASE-NOTES 22 Jul 2005 13:07:52 -  1.26
  @@ -29,7 +29,7 @@
   ===
   Tomcat 5.5 is designed to run on J2SE 5.0 and later, and requires
   configuration to run on J2SE 1.4.  Make sure to read the RUNNING.txt 
  -file in this directory if you are using J2SE 1.4.
  +file in the fulldocs downloadable file(s) if you are using J2SE 1.4.
   
   In addition, Tomcat 5.5 uses the Eclipse JDT Java compiler for compiling
   JSP pages.  This means you no longer need to have the complete
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2005-01-19 Thread remm
remm2005/01/19 12:30:26

  Modified:webapps/docs changelog.xml
   .RELEASE-NOTES
  Log:
  - Small tweaks and changelog updates.
  
  Revision  ChangesPath
  1.225 +4 -1  jakarta-tomcat-catalina/webapps/docs/changelog.xml
  
  Index: changelog.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v
  retrieving revision 1.224
  retrieving revision 1.225
  diff -u -r1.224 -r1.225
  --- changelog.xml 18 Jan 2005 22:16:24 -  1.224
  +++ changelog.xml 19 Jan 2005 20:30:26 -  1.225
  @@ -26,7 +26,7 @@
 /p
   /section
   
  -section name=Tomcat 5.5.7 (yoavs)
  +section name=Tomcat 5.5.7 (remm)
 subsection name=General
   changelog
 add
  @@ -43,6 +43,9 @@
 fix
   bug32953/bug: SERVLETAPI: XSS Issues, submitted by Mark Thomas 
(jfarcand)
 /fix
  +  update
  +Update to commons-digester 1.6, JDT 3.0.1, MX4J 2.1.0, Struts 1.2.6 
(remm)
  +  /update
   /changelog
 /subsection
   
  
  
  
  1.25  +2 -3  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- RELEASE-NOTES 9 Sep 2004 16:56:59 -   1.24
  +++ RELEASE-NOTES 19 Jan 2005 20:30:26 -  1.25
  @@ -67,12 +67,11 @@
   A standard installation of Tomcat 5.5 makes all of the following APIs 
available
   for 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)
  +* commons-logging-api.jar (Commons Logging API 1.0.x)
   * 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)
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2004-09-09 Thread yoavs
yoavs   2004/09/09 09:56:59

  Modified:.RELEASE-NOTES
  Log:
  Took out stale and irrelevant section (for Tomcat 5.5, still relevant for 5.0 and 
prior releases) about javac leaking memory.
  
  Revision  ChangesPath
  1.24  +1 -15 jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- RELEASE-NOTES 30 Aug 2004 21:32:04 -  1.23
  +++ RELEASE-NOTES 9 Sep 2004 16:56:59 -   1.24
  @@ -15,7 +15,6 @@
   * JNI Based Applications
   * Bundled APIs
   * Web application reloading and static fields in shared libraries
  -* JAVAC leaking memory
   * Tomcat on Linux
   * Enabling SSI and CGI Support
   * Security manager URLs
  @@ -106,19 +105,6 @@
   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).
  -
  -
  -=
  -JAVAC leaking memory:
  -=
  -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
  -freed by stopping Tomcat and then restarting it.
  -
  -The JSP command line compiler (JSPC) can also be used to precompile the JSPs.
  -
  -Note: This issue has been fixed in Sun JDK 1.4.x.
   
   
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2004-08-30 Thread remm
remm2004/08/30 14:32:04

  Modified:.RELEASE-NOTES
  Log:
  - A lot of information seemed stale, as we voted to use the API from J2SE 1.4.
  
  Revision  ChangesPath
  1.23  +17 -51jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- RELEASE-NOTES 30 Aug 2004 17:36:48 -  1.22
  +++ RELEASE-NOTES 30 Aug 2004 21:32:04 -  1.23
  @@ -14,7 +14,6 @@
   * Dependency Changes
   * JNI Based Applications
   * Bundled APIs
  -* XML Parsers
   * Web application reloading and static fields in shared libraries
   * JAVAC leaking memory
   * Tomcat on Linux
  @@ -30,21 +29,21 @@
   Dependency Changes:
   ===
   Tomcat 5.5 is designed to run on J2SE 5.0 and later, and requires
  -configuration to run on J2SE versions 1.3 and 1.4.  Make sure to 
  -read the RUNNING.txt file in this directory if you are using
  -J2SE version 1.3 or 1.4.
  +configuration to run on J2SE 1.4.  Make sure to read the RUNNING.txt 
  +file in this directory if you are using J2SE 1.4.
   
  -In addition, Tomcat 5.5 depends on the Eclipse JDT for compiling
  +In addition, Tomcat 5.5 uses the Eclipse JDT Java compiler for compiling
   JSP pages.  This means you no longer need to have the complete
   Java Development Kit (JDK) to run Tomcat, but a Java Runtime Environment
  -(JRE) is sufficient.  The Eclipse JDT is bundled with the binary
  -Tomcat distributions.
  +(JRE) is sufficient.  The Eclipse JDT Java compiler is bundled with the 
  +binary Tomcat distributions.  Tomcat can also be configured to use the
  +compiler from the JDK to compile JSPs, or any other Java compiler supported 
  +by Apache Ant.
   
   
   ===
   JNI Based Applications:
   ===
  -
   Applications that require native libraries must ensure that the libraries have
   been loaded prior to use.  Typically, this is done with a call like:
   
  @@ -66,7 +65,6 @@
   =
   Bundled APIs:
   =
  -
   A standard installation of Tomcat 5.5 makes all of the following APIs available
   for use by web applications (by placing them in common/lib or shared/lib):
   * commons-el.jar (Commons Expression Language 1.0)
  @@ -82,7 +80,8 @@
   * naming-resources.jar (JNDI DirContext implementations)
   * servlet-api.jar (Servlet 2.4 API)
   
  -Installing the compatibility package will add the following to the list:
  +Installing the compatibility package will add the following to the list, which are
  +needed 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)
   
  @@ -90,32 +89,14 @@
   putting unpacked classes into a classes directory (not created by default),
   or by placing them in JAR files in the lib directory.
   
  -To override the XML parser implementation or interfaces, see the section below.
  -
  -Please note that the JMX API is required by Tomcat while starting up, and thus
  -is in Tomcat's bootstrap classpath and placed in the $CATALINA_HOME/bin directory.
  -
  -
  -
  -XML Parsers:
  -
  -
  -As described above, Tomcat 5.5 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
  -XML parser, as long as it is compatible with the JAXP 1.2 APIs.
  -
  -On a related note, JDK 1.4 includes Xalan.  If you run into Xalan-related
  -problems, try downloading the latest Xalan version (from 
  -http://xml.apache.org/xalan-j/index.html) and placing the Xalan jar file
  -in the common/endorsed directory.
  +To override the XML parser implementation or interfaces, use the endorsed
  +mechanism 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 objects
   instantiated by the web application. To avoid class loading related problems
   (ClassCastExceptions, messages indicating that the classloader
  @@ -130,7 +111,6 @@
   =
   JAVAC leaking memory:
   =
  -
   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
  @@ -144,26 +124,17 @@
   
   Tomcat on 

cvs commit: jakarta-tomcat-5 RELEASE-NOTES build.properties.default

2004-06-15 Thread yoavs
yoavs   2004/06/15 11:42:06

  Modified:.RELEASE-NOTES build.properties.default
  Log:
  Updated commons-collections dependency to 2.1.1, updated release notes to more 
accurately describe common library versions.
  
  Revision  ChangesPath
  1.18  +6 -6  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- RELEASE-NOTES 28 May 2004 15:57:44 -  1.17
  +++ RELEASE-NOTES 15 Jun 2004 18:42:06 -  1.18
  @@ -53,12 +53,12 @@
   
   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 1.6)
  -* commons-collections.jar (Commons Collections 2.1)
  -* commons-dbcp.jar (Commons DBCP 1.1)
  +* ant.jar (Apache Ant 1.6 or later)
  +* commons-collections*.jar (Commons Collections 2.1 or later)
  +* commons-dbcp.jar (Commons DBCP 1.1 or later)
   * commons-el.jar (Commons Expression Language 1.0)
  -* commons-logging-api.jar (Commons Logging API 1.0.3)
  -* commons-pool.jar (Commons Pool 1.1)
  +* commons-logging-api.jar (Commons Logging API 1.0.3 or later)
  +* commons-pool.jar (Commons Pool 1.1 or later)
   * jasper-compiler.jar (Jasper 2 Compiler)
   * jasper-runtime.jar (Jasper 2 Runtime)
   * jsp-api.jar (JSP 2.0 API)
  
  
  
  1.127 +4 -4  jakarta-tomcat-5/build.properties.default
  
  Index: build.properties.default
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/build.properties.default,v
  retrieving revision 1.126
  retrieving revision 1.127
  diff -u -r1.126 -r1.127
  --- build.properties.default  15 Jun 2004 18:14:39 -  1.126
  +++ build.properties.default  15 Jun 2004 18:42:06 -  1.127
  @@ -61,10 +61,10 @@
   
   
   # - Commons Collections, version 2.0 or later -
  -commons-collections.home=${base.path}/commons-collections-2.1
  +commons-collections.home=${base.path}/commons-collections-2.1.1
   commons-collections.lib=${commons-collections.home}
  -commons-collections.jar=${commons-collections.lib}/commons-collections.jar
  
-commons-collections.loc=${base-jakarta.loc}/commons/collections/binaries/collections-2.1.tar.gz
  +commons-collections.jar=${commons-collections.lib}/commons-collections-2.1.1.jar
  
+commons-collections.loc=${base-jakarta.loc}/commons/collections/binaries/commons-collections-2.1.1.tar.gz
   
   
   # - Commons Launcher, version 0.9 or later -
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2004-05-28 Thread yoavs
yoavs   2004/05/28 08:57:44

  Modified:.RELEASE-NOTES
  Log:
  Added release notes note about jmx.jar in bootstrap classpath.
  
  Revision  ChangesPath
  1.17  +6 -1  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- RELEASE-NOTES 26 May 2004 13:02:44 -  1.16
  +++ RELEASE-NOTES 28 May 2004 15:57:44 -  1.17
  @@ -75,6 +75,11 @@
   Tomcat 5.0 also makes Xerces 2 and the Commons Logging API (release 1.0.3)
   available to web applications.
   
  +Please note that the JMX API is available to applications as well.  The jmx.jar
  +file used to be located in the common/lib directory, but was moved to the bin
  +directory as part of the Tomcat 5.0.20 release.  The jmx.jar is in Tomcat's
  +bootstrap classpath (included via the Class Path line in bootstrap.jar's manifest).
  +
   
   --
   Tomcat 5.0 and XML Parsers:
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2004-05-26 Thread yoavs
yoavs   2004/05/26 06:02:44

  Modified:.RELEASE-NOTES
  Log:
  - Updated Xerces version reference from 2.6.0 to 2.6.2
  
  Revision  ChangesPath
  1.16  +2 -2  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- RELEASE-NOTES 17 May 2004 23:43:33 -  1.15
  +++ RELEASE-NOTES 26 May 2004 13:02:44 -  1.16
  @@ -86,7 +86,7 @@
   you may replace the xercesImpl.jar file in common/endorsed with another
   XML parser, as long as it is compatible with the JAXP 1.2 APIs.
   
  -Xerces 2.6.0 is included.
  +Xerces 2.6.2 is included.
   
   
   ---
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2004-03-22 Thread remm
remm2004/03/22 10:51:50

  Modified:.RELEASE-NOTES
  Log:
  - Add a note that JMX is required and that there's no Win installer.
  
  Revision  ChangesPath
  1.13  +17 -3 jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- RELEASE-NOTES 14 Jan 2004 13:30:02 -  1.12
  +++ RELEASE-NOTES 22 Mar 2004 18:51:50 -  1.13
  @@ -11,6 +11,7 @@
   KNOWN ISSUES IN THIS RELEASE:
   
   
  +* JMX required
   * Tomcat 5.0 and JNI Based Applications
   * Tomcat 5.0 Standard APIs Available
   * Tomcat 5.0 and XML Parsers
  @@ -24,6 +25,20 @@
   * When all else fails
   
   
  +
  +JMX required
  +
  +
  +Due to new licensing guidelines mandated by the Apache Software
  +Foundation Board of Directors, a JMX implementation can no longer
  +be distributed with the Apache Tomcat binaries. As a result, you
  +must download a JMX 1.2 implementation (such as the Sun Reference
  +Implementation) and copy the JAR containing the API and
  +implementation of the JMX specification to: ${catalina.home}/bin/jmx.jar
  +
  +For similar reasons, a Windows installer for Tomcat is no longer available.
  +
  +
   -
   Tomcat 5.0 and JNI Based Applications:
   -
  @@ -52,7 +67,7 @@
   
   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)
  +* ant.jar (Apache Ant 1.6)
   * commons-collections.jar (Commons Collections 2.1)
   * commons-dbcp.jar (Commons DBCP 1.1)
   * commons-el.jar (Commons Expression Language 1.0)
  @@ -60,7 +75,6 @@
   * commons-pool.jar (Commons Pool 1.1)
   * jasper-compiler.jar (Jasper 2 Compiler)
   * jasper-runtime.jar (Jasper 2 Runtime)
  -* jmx.jar (Sun JMX RI 1.2)
   * jsp-api.jar (JSP 2.0 API)
   * commons-el.jar (JSP 2.0 Expression Language)
   * naming-common.jar (JNDI Context implementation)
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2004-01-14 Thread remm
remm2004/01/14 05:30:02

  Modified:.RELEASE-NOTES
  Log:
  - Update Xerces version.
  
  Revision  ChangesPath
  1.12  +2 -2  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- RELEASE-NOTES 29 Nov 2003 20:11:10 -  1.11
  +++ RELEASE-NOTES 14 Jan 2004 13:30:02 -  1.12
  @@ -86,7 +86,7 @@
   you may replace the xercesImpl.jar file in common/endorsed with another
   XML parser, as long as it is compatible with the JAXP 1.2 APIs.
   
  -Xerces 2.5.0 is included.
  +Xerces 2.6.0 is included.
   
   
   ---
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-11-29 Thread funkman
funkman 2003/11/29 12:11:11

  Modified:.RELEASE-NOTES
  Log:
  The line numbers for uncommenting cgi and ssi keeps on getting out
  of sync with web.xml. An attempt at rewording to not have them
  get out of sync.
  
  Revision  ChangesPath
  1.11  +40 -18jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- RELEASE-NOTES 25 Nov 2003 14:57:59 -  1.10
  +++ RELEASE-NOTES 29 Nov 2003 20:11:10 -  1.11
  @@ -72,7 +72,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 Xerces 2 and the Commons Logging API (release 1.0.3)  
  +Tomcat 5.0 also makes Xerces 2 and the Commons Logging API (release 1.0.3)
   available to web applications.
   
   
  @@ -123,17 +123,17 @@
   ---
   
   Virtual machine crashes can 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. At bash shell, 
  +The problems can be fixed by reducing the default stack size. At bash shell,
   do 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
   
  -Additionally, Redhat Linux 9.0 users should use the same setting, to avoid 
  +Additionally, Redhat Linux 9.0 users should use the same setting, to avoid
   stability problems.
   
   
  @@ -147,25 +147,47 @@
   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:
  -* 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
  -  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:
  +To enable CGI:
   * rename the file $CATALINA_HOME/server/lib/servlets-cgi.renametojar to
 $CATALINA_HOME/server/lib/servlets-cgi.jar.
  +* in $CATALINA_HOME/conf/web.xml, you will need to uncomment 2 areas, the
  +  servlet declaration and the servlet mapping. The servlet declaration
  +  looks similar to this:
  +servlet
  +servlet-namecgi/servlet-name
  +...
  +/servlet
  +
  +  While the servlet mapping looks similar to this:
  +servlet-mapping
  +servlet-namecgi/servlet-name
  +url-pattern/cgi-bin/*/url-pattern
  +/servlet-mapping
  +
  +  Alternately, these servlet declarations and mappings
  +  can be added to your web application deployment descriptor.
  +
  +To enable SSI:
   * 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 226 and 250, as well as the associated servlet mappings
  -  on lines 276 and 294. Alternately, these servlet declarations and mappings 
  +* in $CATALINA_HOME/conf/web.xml, you will need to uncomment 2 areas, the
  +  servlet declaration and the servlet mapping. The servlet declaration
  +  looks similar to this:
  +servlet
  +servlet-namessi/servlet-name
  +...
  +/servlet
  +
  +  While the servlet mapping looks similar to this:
  +servlet-mapping
  +servlet-namessi/servlet-name
  +url-pattern*.shtml/url-pattern
  +/servlet-mapping
  +
  +  Alternately, these servlet declarations and mappings
 can be added to your web application deployment descriptor.
  +
   
   
   -
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-11-25 Thread remm
remm2003/11/25 06:05:17

  Modified:.RELEASE-NOTES
  Log:
  - Release notes update.
  
  Revision  ChangesPath
  1.9   +21 -17jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- RELEASE-NOTES 8 Sep 2003 13:49:23 -   1.8
  +++ RELEASE-NOTES 25 Nov 2003 14:05:17 -  1.9
  @@ -16,7 +16,7 @@
   * Tomcat 5.0 and XML Parsers
   * Web application reloading and static fields in shared libraries
   * JAVAC leaking memory
  -* Linux and Sun JDK 1.2.x - 1.3.x
  +* Tomcat on Linux
   * Enabling SSI and CGI Support
   * Security manager URLs
   * Symlinking static resources
  @@ -54,9 +54,10 @@
   for use by web applications (by placing them in common/lib or shared/lib):
   * ant.jar (Apache Ant)
   * commons-collections.jar (Commons Collections 2.1)
  -* commons-dbcp.jar (Commons DBCP 1.0)
  +* commons-dbcp.jar (Commons DBCP 1.1)
   * commons-el.jar (Commons Expression Language 1.0)
  -* commons-pool.jar (Commons Pool 1.0)
  +* commons-logging-api.jar (Commons Logging API 1.0.3)
  +* commons-pool.jar (Commons Pool 1.1)
   * jasper-compiler.jar (Jasper 2 Compiler)
   * jasper-runtime.jar (Jasper 2 Runtime)
   * jmx.jar (Sun JMX RI 1.2)
  @@ -115,21 +116,24 @@
   Note: This issue has been fixed in Sun JDK 1.4.x.
   
   
  
  -Linux and Sun JDK 1.2.x - 1.3.x:
  
  +---
  +Tomcat on Linux:
  +---
   
  -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
  +Virtual machine crashes can 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. From a bash shell,
  -use ulimit -s 2048; use limit stacksize 2048 for tcsh.
  +The problems can be fixed by reducing the default stack size. At bash shell, 
  +do 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
   
  +Additionally, Redhat Linux 9.0 users should use the same setting, to avoid 
  +stability problems.
  +
   
   
   Enabling SSI and CGI Support:
  @@ -148,8 +152,8 @@
 %CATALINA_HOME%\server\lib\servlets-ssi.jar.
   * in %CATALINA_HOME%\conf\web.xml, uncomment the servlet declarations starting
 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.
  +  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:
   * rename the file $CATALINA_HOME/server/lib/servlets-cgi.renametojar to
  @@ -158,8 +162,8 @@
 $CATALINA_HOME/server/lib/servlets-ssi.jar.
   * in $CATALINA_HOME/conf/web.xml, uncomment the servlet declarations starting
 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.
  +  on lines 276 and 294. Alternately, these servlet declarations and mappings 
  +  can be added to your web application deployment descriptor.
   
   
   -
  @@ -181,8 +185,8 @@
   Symlinking static resources:
   ---
   
  -By default, Unix symlinks will not work when used in a web application to link 
resources
  -located outside the web application root directory.
  +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
   the check.
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-09-08 Thread remm
remm2003/09/08 06:49:23

  Modified:.RELEASE-NOTES
  Log:
  - Update the classloader contents.
  
  Revision  ChangesPath
  1.8   +4 -5  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- RELEASE-NOTES 6 Sep 2003 17:50:07 -   1.7
  +++ RELEASE-NOTES 8 Sep 2003 13:49:23 -   1.8
  @@ -56,12 +56,10 @@
   * commons-collections.jar (Commons Collections 2.1)
   * commons-dbcp.jar (Commons DBCP 1.0)
   * commons-el.jar (Commons Expression Language 1.0)
  -* commons-logging-api.jar (Commons Logging 1.0.3)
   * commons-pool.jar (Commons Pool 1.0)
   * 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)
  +* jmx.jar (Sun JMX RI 1.2)
   * jsp-api.jar (JSP 2.0 API)
   * commons-el.jar (JSP 2.0 Expression Language)
   * naming-common.jar (JNDI Context implementation)
  @@ -73,7 +71,8 @@
   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 Xerces 2 available to web applications.
  +Tomcat 5.0 also makes Xerces 2 and the Commons Logging API (release 1.0.3)  
  +available to web applications.
   
   
   --
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-09-06 Thread remm
remm2003/09/06 10:50:07

  Modified:.RELEASE-NOTES
  Log:
  - Remove release notes entry.
  
  Revision  ChangesPath
  1.7   +1 -13 jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- RELEASE-NOTES 30 Aug 2003 21:03:50 -  1.6
  +++ RELEASE-NOTES 6 Sep 2003 17:50:07 -   1.7
  @@ -21,7 +21,6 @@
   * Security manager URLs
   * Symlinking static resources
   * Enabling invoker servlet
  -* Privileged web applications and log4j
   * When all else fails
   
   
  @@ -201,17 +200,6 @@
   
   Using the invoker servlet in a production environment is not recommended and
   is unsupported.
  -
  -
  --
  -Privileged web applications and log4j:
  --
  -
  -Apache log4j, or other logging systems, cannot be used inside privileged web
  -applications, due to classloading problems caused by commons-logging.
  -
  -Note that privileged contexts are only useful to write web application which
  -extend the container functionality.
   
   
   ---
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-08-30 Thread remm
remm2003/08/30 14:03:51

  Modified:.RELEASE-NOTES
  Log:
  - Update release notes.
  
  Revision  ChangesPath
  1.6   +9 -27 jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- RELEASE-NOTES 25 Aug 2003 18:43:44 -  1.5
  +++ RELEASE-NOTES 30 Aug 2003 21:03:50 -  1.6
  @@ -21,9 +21,7 @@
   * Security manager URLs
   * Symlinking static resources
   * Enabling invoker servlet
  -* Container provided authentication
  -* Administration web application
  -* Deployment descriptors validation
  +* Privileged web applications and log4j
   * When all else fails
   
   
  @@ -205,31 +203,15 @@
   is unsupported.
   
   
  --
  -Container provided authentication:
  --
  -
  -Support for the Servlet API PFD 3 specification may not be complete yet for
  -security constraint matching. This will be resolved in a future Tomcat beta
  -release.
  -
  -
  ---
  -Administration web application:
  ---
  -
  -Due to changes in the configuration file format, the administration web 
  -application does not support editing hosts or connectors. This will be 
  -resolved in a future Tomcat beta release.
  -
  +-
  +Privileged web applications and log4j:
  +-
   
  --
  -Deployment descriptors validation:
  --
  +Apache log4j, or other logging systems, cannot be used inside privileged web
  +applications, due to classloading problems caused by commons-logging.
   
  -Validation of Servlet 2.4 and JSP 2.0 deployment descriptors (using XML 
  -schema for validation) does not properly work at this time. The cause of this
  -problem is investigated.
  +Note that privileged contexts are only useful to write web application which
  +extend the container functionality.
   
   
   ---
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-08-25 Thread remm
remm2003/08/25 11:43:44

  Modified:.RELEASE-NOTES
  Log:
  - Add new release notes on the current outstanding issues.
  
  Revision  ChangesPath
  1.5   +42 -8 jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- RELEASE-NOTES 24 Jul 2003 12:01:14 -  1.4
  +++ RELEASE-NOTES 25 Aug 2003 18:43:44 -  1.5
  @@ -21,6 +21,10 @@
   * Security manager URLs
   * Symlinking static resources
   * Enabling invoker servlet
  +* Container provided authentication
  +* Administration web application
  +* Deployment descriptors validation
  +* When all else fails
   
   
   -
  @@ -52,11 +56,11 @@
   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-collections.jar (Commons Collections 2.1)
   * 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)
  +* commons-logging-api.jar (Commons Logging 1.0.3)
  +* commons-pool.jar (Commons Pool 1.0)
   * jasper-compiler.jar (Jasper 2 Compiler)
   * jasper-runtime.jar (Jasper 2 Runtime)
   * jmx.jar (From mx4j-1.1.1)
  @@ -64,7 +68,7 @@
   * 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)
  +* naming-factory.jar (JNDI object factories for J2EE ENC support)
   * naming-resources.jar (JNDI DirContext implementations)
   * servlet-api.jar (Servlet 2.4 API)
   
  @@ -83,7 +87,7 @@
   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
  -XML parser, as long as it is compatible with the JAXP 1.1 APIs.
  +XML parser, as long as it is compatible with the JAXP 1.2 APIs.
   
   
   ---
  @@ -112,6 +116,8 @@
   
   The JSP command line compiler (JSPC) can also be used to precompile the JSPs.
   
  +Note: This issue has been fixed in Sun JDK 1.4.x.
  +
   
   ---
   Linux and Sun JDK 1.2.x - 1.3.x:
  @@ -199,8 +205,36 @@
   is unsupported.
   
   
  -
  +-
  +Container provided authentication:
  +-
  +
  +Support for the Servlet API PFD 3 specification may not be complete yet for
  +security constraint matching. This will be resolved in a future Tomcat beta
  +release.
  +
  +
  +--
  +Administration web application:
  +--
  +
  +Due to changes in the configuration file format, the administration web 
  +application does not support editing hosts or connectors. This will be 
  +resolved in a future Tomcat beta release.
  +
  +
  +-
  +Deployment descriptors validation:
  +-
  +
  +Validation of Servlet 2.4 and JSP 2.0 deployment descriptors (using XML 
  +schema for validation) does not properly work at this time. The cause of this
  +problem is investigated.
  +
  +
  +---
   When all else fails:
  -
  +---
  +
   See the FAQ
   http://jakarta.apache.org/tomcat/faq/
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-07-24 Thread funkman
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  ChangesPath
  1.4   +30 -20jakarta-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 -  1.3
  +++ RELEASE-NOTES 24 Jul 2003 12:01:14 -  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.
   * 

cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2003-06-25 Thread yoavs
yoavs   2003/06/25 17:03:49

  Modified:.RELEASE-NOTES
  Log:
  Fixed bug 19939
  
  Revision  ChangesPath
  1.3   +17 -17jakarta-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 -   1.2
  +++ RELEASE-NOTES 26 Jun 2003 00:03:49 -  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 

cvs commit: jakarta-tomcat-5 RELEASE-NOTES build.properties.default build.xml

2003-02-04 Thread luehe
luehe   2003/02/04 15:41:01

  Modified:.RELEASE-NOTES build.properties.default build.xml
  Log:
  Integrated commons-el
  
  Revision  ChangesPath
  1.2   +2 -2  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- RELEASE-NOTES 9 Oct 2002 10:06:07 -   1.1
  +++ RELEASE-NOTES 4 Feb 2003 23:41:01 -   1.2
  @@ -59,7 +59,7 @@
   * jasper-compiler.jar (Jasper 2 Compiler)
   * jasper-runtime.jar (Jasper 2 Runtime)
   * jsp-api.jar (JSP 2.0 API)
  -* jsp20el.jar (JSP 2.0 Expression Language)
  +* commons-el.jar (JSP 2.0 Expression Language)
   * naming-common.jar (JNDI Context implementation)
   * naming-factory.jar (JNDI object factories)
   * naming-resources.jar (JNDI DirContext implementations)
  
  
  
  1.65  +9 -1  jakarta-tomcat-5/build.properties.default
  
  Index: build.properties.default
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/build.properties.default,v
  retrieving revision 1.64
  retrieving revision 1.65
  diff -u -r1.64 -r1.65
  --- build.properties.default  31 Jan 2003 19:01:56 -  1.64
  +++ build.properties.default  4 Feb 2003 23:41:01 -   1.65
  @@ -74,6 +74,14 @@
   commons-digester.loc=jakarta-commons/digester
   
   
  +# - Commons Expression Language (EL) -
  +commons-el.home=${base.path}/commons-el
  +commons-el.lib=${commons-el.home}
  +commons-el.jar=${commons-el.lib}/commons-el.jar
  +commons-el.loc=jakarta-commons/el
  +commons-el.cvs.loc=jakarta-commons/el
  +
  +
   # - Commons Logging, version 1.0.1 or later -
   commons-logging.home=${base.path}/commons-logging-1.0.2
   commons-logging.lib=${commons-logging.home}
  
  
  
  1.75  +6 -0  jakarta-tomcat-5/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
  retrieving revision 1.74
  retrieving revision 1.75
  diff -u -r1.74 -r1.75
  --- build.xml 31 Jan 2003 18:55:04 -  1.74
  +++ build.xml 4 Feb 2003 23:41:01 -   1.75
  @@ -1013,6 +1013,12 @@
 param name=destfile value=${commons-modeler.jar}/
   /antcall
   
  +antcall target=cvsbuild
  +  param name=location value=${commons-el.cvs.loc}/
  +  param name=subdir value=${commons-el.home}/
  +  param name=destfile value=${commons-el.jar}/
  +/antcall
  +
   antcall target=downloadfile
 param name=sourcefile value=${nsis.loc}/
 param name=destfile value=${nsis.exe}/
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]