Originally posted by Ilari Moilanen:
The jsp in question is a different one from the one he is trying to access so I don't think that this is the problem here. Don't know why the index.jsp is mapped as it is tough...
By the way, can you access that servlet that is mapped there? if you can then you know that the problem is with jsp pages only and not with ordinary servlets...
One thing that comes to mind is to add this servlet mapping to your servlet mappings in web.xml
You should have one. if for nothing else than to make sure that your app is deployed as a Servlets 2.4 app which will enable JSP 2.0 mechanisms.Originally posted by K DeLucia:
Do I need a web.xml for my application? I don't have one on my PC, but I've seen it said that it's required and that it's not
No. JSPs can be directly addressed (unless you want to hide them as part of an MVC solution -- but that's later...).If it is required, do I need to somehow define my jsp in it?
Only when you add servlets. (Something you should think about soon since all modern best practice web app structures utilize servlets.) Servlets must be declared and mapped in the deployment descriptor.Do I need a servlet entry?
Context entries are added in their own folder. They may not be necessary for a straight-forward context deployed under webapps.(I don't use a servlet, just some jsp pages and some javabeans). Do I need to make changes to the server.xml? (I've seen references to adding a context entry).
You should only need to have JAVA_HOME defined. By the way, case counts. Don't be sloppy either in your code or posts.Do I need all three environment variables Cataline_Home, Java_Home and Classpath
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |