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
