You're right, saying the app 'quit' does not convey much meaningful information. I've had my coffee this morning so I should be a little better.
To begin, I have a jsf web project that works fine. However, when I add the following to my web.xml and redeploy the project, it's as if the request never makes it to the servlet. When I type (using your example) http://localhost/test/index.jsf, or http://localhost/test/faces/index.jsp or http://localhost/test/faces/index.jsf, nothing happens on the server side and no logs are generated. However, if I type http://localhost/test/index.jsp, the server throws the following exception and stack trace. At this point, I'm starting realize that this problem has less to do with myFaces and is probably due to my relative inexperience with JSF in general. Thanks for your help and suggestions so far! FINE: Can't leverage base class javax.servlet.jsp.JspException: Cannot find FacesContext at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:405) at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105) at org.apache.jsp.index_jsp._jspx_meth_f_view_0(org.apache.jsp.index_jsp:12 9) at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:105) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:322) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1 48) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:85 6) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint .java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow erWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:684) at java.lang.Thread.run(Thread.java:595) -----Original Message----- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Thursday, October 13, 2005 10:19 PM To: MyFaces Discussion Subject: Re: Bewildered by JSCookMenu James Reynolds wrote: > Thanks Simon, > > I had overlooked the Extensions Filter page on the site. Having read > it, I've a much better understanding about what it's doing. > > However, when I add the necessary parts to my Web.xml, my app breaks. > I've watched the FINE logging entries go by in my console when I start > the app. It gets as far as starting the server, but then it > inexplicably quits and the browser shows a 404 error. It's as if the > Faces Servlet is never called to action. > > I wonder if it has something to do with my extensions. I'm not using > any .faces or .jsf extensions. All of my files are .jsp exertions. > Should I be using a different server mapping? Even when your template files are .jsp files, the browser needs to request them as .jsf pages. eg you have page "foo.jsp" in a webapp named "test". You point the browser to "http://localhost/test/foo.jsf". Note the "jsf" at the end of the URL. Without that, the faces servlet never gets run and nothing will work at all. I have no idea what you mean by "my app quits". If you're using Apache Tomcat or JBoss or something and the application actually *terminates* then that is a major major major bug in that servlet engine [extremely unlikely]. Or you've got a broken java installation or something. > > Another thought I had is if the problem is with my jsf libraries. I'm > using the jsf-api.jar and the jsf-impl.jar. Am I required to use the > myfaces implementations to make it work? You mean you're using the Sun reference implementation and trying to run the tomahawk libraries on that? According to the tomahawk page on the myfaces website, tomahawk is "100% supported" on sun's RI for JSF 1.1. Just check you're not running the beta of the Sun JSF 1.2 implementation...that might not be supported yet. I suspect that most people are using tomahawk on MyFaces though... Regards, Simon