You *are* right in saying that there is no additional configuration necessary for Tomcat to serve JSP files. The way I see it, there are several possibilities:
1. If you say that you can access your web application servlets, that means that your web application has been deployed correctly. This means that the 404 error is not related to that reason (if indeed your servlets can be accessed)
2. If you changed the filename and filename extension (i.e. changed it from open.jsp tp open.txt or open.html), and you still cannot even find the page, 2 possibilities come to my mind :
- your URL is wrong : that is, if your web application is called EBook and the servlets are accessed using the URL http://localhost/EBook/servlet/someservlet, then your JSP file can only be accessed using the URL http://localhost/EBook/open.jsp. Ok, say you don't want to go through Apache, then you type http://localhost:8080/EBook/open.jsp. Notice that in both cases, you don't use the invoker (i.e. no "servlet" in the URL). Using the invoker is wrong for JSPs.
- you mistyped the filename. This is not so uncommon as you might think. The problem is that, depending on your browser, the browser may cache the results. For example, if you are using Mozilla, if you get a 404 error once and re-type the URL again, you will always get a 404 error, until you clear your cache! Make sure you clear your cache before you try accessing the page again.
3. You must be very tired and frustrated. Try taking a long break, go for a run or something. Then come back to try again. You may even get the whole thing working automagically !
I have written a step by step on deploying web applications at http://cymulacrum.net/tomcat_toc.html because I thought this was the weakest part of the Tomcat documentation. Try working through my toy example there and see if it works.
Regards, pascal chong
Jerry Ford wrote:
Yes, I agree, Apache is an unnecessary complication for the moment and I am focused now on getting things to work through port 8080.
But Tomcat does serve up pages when I run the app through Apache---for one thing, the error messages are Tomcat-generated, not Apache, and for another, the servlets do work, which Apache cannot make happen without Tomcat.
I don't fully understand the invoker servlet myself, but here's what I think I know:
The invoker mapping only applies to servlets, not html or jsps, and the servlets are working (at least through Apache). If the invoker mapping specifies /servlets/* then "servlets" must be included in the URL. By taking it out of the invoker mapping, it does not need to be included in the URL. So, http://localhost/servlets/do_something is required if the mapping is as you say it should be, and http://localhost/do_something is the URL if the mapping is as I have it.
Is that not correct?
Jerry
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
