This started out being a question about configuring a custom 404 error page when the URL doesn't match a webapp context, but has morphed.
I have Tomcat 6. I haven't actually deployed my web app yet. I've got the docs app, the manager app, and the "Welcome to Tomcat!" ROOT app.
Regarding my original problem, adding a simple custom error html page and adding the <error-page> element to web.xml didn't work (still get tomcat default 404 page with http://localhost:8080/anything).
All of these are related to the display of the welcome page.
Nothing else displays.
Now, it's quite possible that I hosed something while playing around trying to figure out where to put the custom error pages, but WHAT could I have hosed? I've tried removing the temp file, removing the work file, restarting tomcat.
This is very frustrating, not to mention a big waste of time for something so simple.
posted 9 years ago
OK, some files but not others because my browser was caching.
But now, after I put everything back the way it was, why:
If I copy everything from the default web.xml into the ROOT webapp's web.xml, does the ROOT webapp stop finding the pages?
The only thing that was in the ROOT webapp was the display-name and the description, and I kept those. It's supposed to take the information from the default one.
Hmm. Maybe relative paths play a role, since the default one was in conf, and the ROOT one is in WEB-INF? No, there are no references that I see to locations on the server. Frustrating.