OOP-Reserch: Tomcat3.1Beta-Index

Tomcat3.1Beta > Index

JServ and Tomcat3.1Beta

Any quetions and comments are welcome to me.
Please make the subject of your mail to begin with 'OOP[tomcat]' (quotes are not required.). I'll reply to you soon.

As you know, JSP and Servlet plays the role of the user interface of J2EE applications. I'm sure that the seriouse system developers in the world are desire for the cool servlet server. And now, Tomcat is available.

Tomcat3.1Beta is the implementation of JavaServerPages1.1 and Servle2.2 specification and developed and maintained by the Jakarta Project.

The Jakarta Project is managed by the Apache Software Foundation, which is very famouse for its http server. The Apache Software Foundation also produces another cool project, the Apache JServ project, whose purpose is to enables us to use the servlet engine from Apache http server. The "JServ", which is the product from the Apache JServ project, consists of the JServ module installed in the Apache http server and its sophisticated servlet engine. 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?

But how wonderfull if the Apache http server redirects them to the Tomcat servlet engine! Through the Apache httpd server, Tomcat can

handle the 'HTTPS' request to the Apache httpd server.
handle the request to the virtual hosts on the Apache httpd server.

And now you can do it. The source distribution of Tomcat3.1Beta includes the source of the JServ module, which works well with Tomcat3.1Beta.

But at this time, there are some restrictions:

Tomcat cannot started by the JServ module at the boot of the Apache http server.
The mapping of the path and the context defined on the JServ module side is not reflected to the Tomcat servlet server. For example, if you map the path of /test to the context of /examples, the request such as http://foo.com/test/myservlet should be redirected to Tomcat as the request to the servle of 'myservlet' in the context of '/examples'. But Tomcat tries to find the servlet of 'myservlet' in the contest of '/mytest', not the mapped context of '/example' and failed to invoke it.
The JServ module cannot obtain the configuration information of the Tomcat servlet server. The request of http://foo.com/jserv/ returns the page reporting the configuration of the JServ module, but the configuration of Tomcat cannot be reported.
This is not the JServ related problem, but Tomcat cannot be configured to bind its socket to the specified IP address. In the configuraiton file of Tomcat, there is no place to specify the IP address which Tomcat listen to, and it always listen to the local host.

To unlock these restrictions, I modified 2 classes of Tomcat3.1Beta and appended 1 class to it. They are:

Modified class
1. org.apache.tomcat.service.connector.Ajp12ConnectionHandler
2. org.apache.tomcat.service.SimpleTcpConnector
Appended class
1. org.apache.tomcat.startup.TomcatJServ

and the source distribution of them are available here.

This documentation describes how to compile the above classes and the required configuarion for JServ and Tomcat3.1Beta.

Java and all Java-based trademarks and logos are trademarks or registered of Sun Microsystems, Inc. in the United States and other countries.

OOP-Reserch HOME

Mail to Me