glenn       01/02/22 19:15:39

  Modified:    .        README.txt
  Log:
  Update with JNDI JDBC DataSource build information
  
  Revision  Changes    Path
  1.12      +9 -9      jakarta-tomcat-4.0/README.txt
  
  Index: README.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-4.0/README.txt,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- README.txt        2001/02/21 03:36:01     1.11
  +++ README.txt        2001/02/23 03:15:39     1.12
  @@ -43,6 +43,15 @@
     installed the distribution.  None of the standard JNDI providers are required
     unless you need them in your own applications.
   
  +* If you want to build in support for JNDI JDBC DataSources you need to
  +  download the following packages and put their jar files in your classpath.
  +
  +  Tyrex http://tyrex.exolab.org/
  +
  +  Java Transaction API (JTA) http://java.sun.com/products/jta
  +
  +  Java JDBC 2.0 Optional Extensions http://java.sun.com/products/jdbc/
  +
   * If you are running a JDK earlier than 1.3, you will also need to place the
     "jndi.jar" file on your CLASSPATH in order to build Tomcat.
   
  @@ -83,15 +92,6 @@
           ./build-regexp.sh       <-- Unix
           build-regexp            <-- Windows
       Set the REGEXP_HOME env variable to point to <install-dir>/bin
  -
  -* If you want to build in support for JNDI JDBC DataSources you need to
  -  download the following packages and put their jar files in your classpath.
  -
  -  Tyrex http://tyrex.exolab.org/
  -
  -  Java Transaction API (JTA) http://java.sun.com/products/jta
  -
  -  Java JDBC 2.0 Optional Extensions http://java.sun.com/products/jdbc/
   
   * Download and install the Servletapi distribution that includes the
     Servlet 2.3 and JSP 1.2 API classes.  A link is available on the Jakarta
  
  
  

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

Reply via email to