This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Two quick checks you need to make. First, on the server, hit your url using port 8080 (the tomcat default) and see if you can access your page.
Also, apache configured to work with mod_jk? The connection will be listed in apache's httpd.conf file. Also, in the httpd.conf, there should be a mapping that tells apache to hand of to tomcat (usually servlet/* and *.jsp). You need to make sure that the mapping in your web.xml matches something that apache will know to hand off.
Joined: Jul 12, 2002
Great reply. Thanks.
Let me give you a bit more detail...
Yes, Apache is configured to run with mod_jk.
Here's a detailed breakdown of my setup (works locally with Just Tomcat and no Apache, naturally...):
Here's the FORM tag from the Hello.jsp that calls the Servlet on it's ON SUBMIT button.
<form ACTION = "/TestServet/HelloWorld">
The actual server directory structure has the WEB-INF folder with web.xml, there's a directory in WEB-INF called classes in which there is the expected directory "TestServlet", in which there is a single class file "HelloWorld.class". This is the standard directory setup.
The Webapp is outside the Webapps folder so there is no "auto-discovery", but the domain is listed in SERVER.XML and is "read in" at Tomcat start time.
Other Java code runs fine on this site, including JDBC and other classes.