Discussions

News: Apache Tomcat 4.0 Final Released

  1. Apache Tomcat 4.0 Final Released (2 messages)

    For those who waited for Tomcat 4.0 - it's official! The Servlet 2.3 and JSP 1.2 specifications are now final, and so is Apache Tomcat 4.0, which implements the new features of these specifications plus a host of other functionality improvements.


    Press Release
    ---------------
    17 September 2001 - Apache Tomcat 4.0 Final Released
    It's official! The Servlet 2.3 and JSP 1.2 specifications are now final, and so is Apache Tomcat 4.0, which implements the new features of these specifications plus a host of other functionality improvements over the current production release (Tomcat 3.2.3). Please read the RELEASE-NOTES-4.0.txt file in the top level directory of the distribution for the latest information on recent changes and known issues. You can also browse the Tomcat 4.0 documentation bundle online at http://jakarta.apache.org.

    Binary distributions of Apache Tomcat 4.0 are available at http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0/.

    Source distributions of Apache Tomcat 4.0 are available at http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0/src/.

    Binary and source distributions of the mod_webapp connector will be posted on Wednesday, September 19, 2001. If you wish to build this connector in the mean time, you can check out the jakarta-tomcat-connectors CVS repository, and follow the directions in the README.txt file in the webapp subdirectory.


    -----------------------------------------------------
  2. Apache Tomcat 4.0 Final Released[ Go to top ]

    Could someone explain me what's new comparing with 3.2.1?
    It's anyone using it on production environment?

    Thankxs,
    Pablo.
  3. But it still has the most annoying problem I've encountered -- you need to restart the server for it to notice new applications, or changes to existing applications. This makes it very hard in a multi-user environment where each user wants their own web apps, such as on university campuses.

    In our case, we have about 200 users with at least one web app each, but most with more, under continual development. We had to resort to restarting the server every half an hour (a long procedure when you have 2000+ contexts).

    What I would like to ask, on behalf of the dept of Computing, Imperial College, is:

    Is there a free JSP/servlet engine which can bolt on to apache and does not have this limitation?

    Until then, Servlets and JSP will be second-class citizens to mpl, php, cgi, and (dare I say it) even ASP.

    Regards,

    Phil