I would try removing the <<context>>.xml file, if there is one, and replace the web.xml with a default one. Then restart Tomcat.

If you still get the 404 error when calling just JSP pages and there are no errors in the catalina.out file then the problem is very likely in the syntax of the URL being used. If this does work then the problem is mostlly in the web.xml file. Possiblly in the <<context>>.xml but not liklly.

The <<context>>.xml file can be found in

<<Tomcat Dir>>Tomcat\conf\Catalina\localhost\<<Name of deployment dir>>.xml

<Sample of a defulat web.xml File>

<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns="http://java.sun.com/xml/ns/j2ee";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";

</Sample of a defulat web.xml File>

Vsevolod (Simon) Ilyushchenko wrote:

Brian Cook wrote on 08/16/2005 10:36 AM:

WOW that looks like a lot lot of unneeded complication.

I do not know if this is absolutely correct for every situation. But it is my experience that if you are just doing JSP pages you do not need the web.xml at all. It is only needed if you need to call a servlet, define a resource like JNDI, or set a context value.

Is the 404 error from Tomcat or Apache? Do you get the 404 error when you try to connect one of the servlets directly?


The error is from Tomcat - if I go to port 8080, I also see it. My issue is that I can't figure out how to turn debug messages on via log4j - I'm sure I'd see something interesting there.


Brian Cook
Digital Services Analyst
Print Time Inc.

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to