 |
: Product by OOP-Research |
 |
: Documentation written by OOP-Research |
 |
: Patch for the other vendor's system |
While this is not the article by OOP-Research, this is one of the best how to for Apache Tomcat 4.x in the world. If you just start the Servlet/JSP development, we strongly recommend you to read this article at least once. Even if you are not familiar with some basic concepts of Servlet/JSP, it will lead you the successful development.
This article is written by Marty Hall, the author of:
- More Servlets and JavaServer Pages
- Core Servlets and JavaServer Pages
- Core Web Programming
, the well-known best-sellers from Prentice Hall and Sun Microsystems Press.
Marty Hall is a Senior Computer Scientist at the Johns Hopkins University Applied Physics Lab, where he designs and develops distributed applications (mostly for government clients) in the Research and Technology Development Center.
In addition to working full-time in research and development using Java and writing Java programming texts, Marty has extensive teaching and training experience, including short courses on JSP and servlets in the US, Japan, Canada, Australia, and the Philippines. For details about his training courses, please visit his web site at:
Tomcat 3.3 is the de facto standard of Servlet 2.2/JSP 1.1 implementation.
Based on the enthusiastic efforts by the cool Apache developers, Tomcat 3.3 provides a very sophisticated modular design, which allows the Servlet container to be customized by adding and removing modules that control the processing of Servlet requests. Now, Tomcat 3.3 gets the significance performance improvements.
By this state-of-art implementation of Servlet 2.2/JSP 1.1, our Servlet/JSP can offer better web-based or WAP-based services than ever.
This article is the How To for setting up Tomcat 3.3 in a secure way.
An object in the ServletContext on Java Servlet can update its enclosing data by accessing SQL database through EJB or JDBC periodically. Our Servlets can get the latest data without the connection to the the SQL.
Un-official extention for Tomcat3.1 is available to download. With this extention, the servlet can access the data of files uploaded by POST with 'multipart/form-data' encoding. It is beyond the Servlets Specification v2.2, but Tomcat can be more usefull.
Tomcat3.1 is the implementation of JavaServerPages1.1 and Servle2.2 specification and developed and maintained by the Jakarta Project. This is an un-official patch for Tomcat3.1.
We, the developers in the Tomcat developer mailing list), have talked about the Servlets Specification v2.2 and JSP Specification v1.1, and I resumed my proposal based on such a discussion. I'm eager to hear your opinion to my proposal!
Tomcat3.1 is the implementation of JavaServerPages1.1 and Servle2.2 specification and developed and maintained by the Jakarta Project.
With the JServ module installed, the Apache http server redirects some of the http request to the JServ servlet engine. This means our servlets can be invoked through the Apache http server. This is cool, ins't it?
This document describes about setting up Tomcat3.1Beta with JServ. Patch for Tomcat3.1Beta is also available in this page.
Building Apache1.3.12 itself easy. But in case many modules need to be compiled with Apache, it is important to take the appropriate procedure. Except for the standard modules which are supplied with Apache source tree, we should carefully examine how to compile them. In this documentation, I'll describe how to compile the following external (non-standard) modules:
- libssl.so
- mod_frontpage.so
- libperl.so
- libdav.so
- mod_fastcgi.so
- libphp3.so
- mod_jserv.so
|