I believe Guy is right: that's the exception that I get when I call a
JSF page outside of the MyFaces context (i.e. I mistakenly type in
MyPage.jsp instead of MyPage.faces)
Have you really mapped the JSP extension to the Faces Servlet? This
is not common practice. Even though the actual filenames may have
the .jsp extension (mine do), there is usually something jsf-specific
as a virtual mapping, e.g. .faces, .jsf, or /faces/*
-- Hi Jeff.
Yes and no: I've put this in my web.xml:
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/Mnemonica/*</url-pattern>
</servlet-mapping>
So the servlet is mapped to anything in the webapp context folder.
(whatever its extension)
@ Guy: just in case (I make mistakes too!) I tried to change the
extension to .jsf like you said, but then I just got all the source
code in my browser. (strange as Tomcat has mime mapping for jsf
files, which are the same as for jsp files)
Wolf
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Wolf Benz wrote:
That's not true, it suffices to map the jsp extention to the
MyFaces Servlet and it will correctly deal with the JSF tags inside.
Besides, otherwise all my other pages wouldn't work either - they
all have jsp extensions.
No, something -I don't know what- makes the treatement of this
errorpage different.
Btw I'm running MyFaces 1.1.4 snapshot. (due other probs not
running v.113)
Wolf
On 23 Aug 2006, at 13:52, Guy Coleman wrote:
If your error page contains JSF then the location should use
the .jsf extension (or whatever url mapping the FacesServlet is
configured to use):
<error-page>
<error-code>404</error-code>
<location>/resources/pages/fileNotFound.jsf</location>
</error-page>
etc.
