Meaningless Drivel is fun!*
The moose likes JSP and the fly likes Mapped JSP Page not showing up on giving the URL pattern Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » JSP
Bookmark "Mapped JSP Page not showing up on giving the URL pattern" Watch "Mapped JSP Page not showing up on giving the URL pattern" New topic
Author

Mapped JSP Page not showing up on giving the URL pattern

Gautam Verma
Greenhorn

Joined: Dec 15, 2010
Posts: 4
The JSP is not showing by giving the URL pattern to which it is mapped in DD.

I have made a very simple application ( It is for testing. )
The directory structure is
JspDemo <- project directory
-- First.jsp (This is in JspDemo.)
-- WEB-INF (This is in JspDemo.)
-- web.xml ( This is in WEB-INF.)


web.xml contains


and First,jsp is a simple JSP which counts number of times it is opened i.e. hits.

Now when i am giving the URL http://localhost:8080/JspDemo/first.jsp
It is giving me the error
HTTP Status 500 with "javax.servlet.ServletException: No servlet class has been specified for servlet First".


And if i am manually calling the JSP by URL http://localhost:8080/JspDemo/First.jsp or loading it on startup by using
load-on-startup tag in DD then it is giving me the error.
Http 404 error with message "Servlet First is not available".

please anyone help me out.
Stefan Evans
Bartender

Joined: Jul 06, 2005
Posts: 1016
The issue is being caused by the metadata-complete="true" attribute on your web.xml.

If you remove that attribute from the web-app element of your web.xml file, it works.

I'm not 100% sure why this works like this. I have never seen this attribute before. According to the documentation:

The metadata-complete attribute defines whether this deployment descriptor and other related deployment
descriptors for this module (e.g., web service descriptors) are complete, or whether the class files available to this
module and packaged with this application should be examined for annotations that specify deployment
information. If metadata-complete is set to "true", the deployment tool must ignore any annotations that specify
deployment information, which might be present in the class files of the application. If metadata-complete is not
specified or is set to "false", the deployment tool must examine the class files of the application for annotations,
as specified by the specifications.


I guess it has something to do with whether or not Tomcat will invoke the translate/compile step for the JSP file.
ie if you are metadata-complete then you shouldn't have to compile anything - right?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Mapped JSP Page not showing up on giving the URL pattern
 
Similar Threads
Jsps and Servlets
JSF runtime error
HTTP Status 404
struts1
Getting error while upgrading my running application from jboss-4.2.1.GA to jboss-6.0.0.Final.