• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

HFSJ-->page 407 Errata...

 
Nicky Eng
Ranch Hand
Posts: 378
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
pick from Errata:
------------------
{407} whole page;
As the .jspf convention is not supported by default in Tomcat, the following mapping
needs to be added to the application's web.xml for the example to work correctly:

<servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jspf</url-pattern>
</servlet-mapping>
-----------------

which web.xml it refers?
 
Darya Akbari
Ranch Hand
Posts: 1855
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Nicky,

the web.xml is meant which you use in you web application. We have only this one web.xml in each application. The one you always place in /WEB-INF/web.xml

Regards,
Darya
 
Nicky Eng
Ranch Hand
Posts: 378
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
oic.
thanks Darya. i thought it was Tomcat's web.xml.....



thanks again.
 
Darya Akbari
Ranch Hand
Posts: 1855
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
 
Alec Lee
Ranch Hand
Posts: 569
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you use <jsp:forward page="header.jspf"/>, the page is not interpreted as JSP page. Because JSP page by default should have extension .jsp. In order to use .jspf, you need to map .jspf extension to the JSP containing class. In tomcat, it is org.apache.jasper.servlet.JspServlet. This class is by default used by the <servlet-name>jsp</servlet-name>. Therefore, all we need is to map .jspf extension to jsp.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic