James Reynolds wrote:
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
Well, the exception you show above is what I would expect when accessing
the .jsp URL directly. Because the faces servlet hasn't run, there is no
FacesContext object stored into the expected threadLocal variable for
the current request thread. So when the JSF component goes looking for
it, the exception gets thrown reporting exactly that.
Why you're seeing nothing at all when accessing the other URLs *when and
only when you have the ExtensionsFilter defined* I don't have any ideas
about. Perhaps you could try writing a very simple filter that writes to
stdout or a logfile whenever it is called, and configure that for the
/faces or *.jsf urls. If you don't get any output from that then you
know the problem is nothing to do with faces at all, but instead some
error in the way you are defining filters.
You should also ensure that you have logging turned up all the way - but
if you're getting log messages at level FINE as shown above then I
presume you've already done that.
Regards,
Simon
