Don't use the apache, switch the Tomcat to 80. Works out of the box like that, and the directions on how are in Goodwill's Apache Jakarta-Tomcat if you want to look at that. It is really obvious, though. Just don't use apache and change 8080 to 80.

At 03:13 PM 10/30/2002 -0700, you wrote:

We've currently got Apache running on HP-UX 11.  Now I'm developing a Struts
webapp that will need to go on the same box.  HP hasn't released Tomcat 4
yet, so we'll have to get it to work ourselves.

Since the Struts app has no static content, is there any reason to put
ourselves through the pain of convincing Apache and Tomcat to play nicely
together?  Or can the two run on the same machine with no knowledge of one
another?

The only disadvantage I see is that my Tomcat URL's will have to include a
port number, since Apache is already listening on port 80.

Anything else I should know?

--
Wendy Smoak
http://sourceforge.net/projects/unidbtags
Micael

-------------------------------------------------------

This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you


--
To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Reply via email to