-
1. Re: [Facelets] XHTML parse error when RichFaces filter in web.xml is specified
honyk Jun 1, 2010 6:10 PM (in response to honyk)Can anybody confirm that RichFaces works properly in Facelets environment?
Can anybody confirm that all this works in NetBeans on Tomcat 6.0?
I am trying to locate the source of problems and then to ask for help in the right community. Now I have no idea what is happening in the background. Can I trace it somehow?
-
2. Re: [Facelets] XHTML parse error when RichFaces filter in web.xml is specified
mkienenb Jun 1, 2010 6:20 PM (in response to honyk)I can confirm that RichFaces works fine with Facelets in a MyFaces 1.2 environment.
Some of our developers use tomcat 6.0. I use Jetty most of the time, but I've used Tomcat at one point to help a fellow developer.
I use eclipse, and as far as I know, no one here is using Netbeans.
myfaces-api-1.2.8.jar
myfaces-impl-1.2.8.jar
richfaces-api-3.3.3.Final.jar
richfaces-impl-3.3.3.Final.jar
richfaces-ui-3.3.3.Final.jar
tomahawk-1.1.9.jar
tomahawk-sandbox-1.1.9.jar
jsf-facelets-1.1.14.jarapache-tomcat-6.0.20
Posting the actual exception will enable people to help you better.
I suspect your problem is that you do not have facelets configured correctly.
Start with a simple facelets project containing only facelets and your JSF implementation. Once you get that working, add in other pieces one at a time.
-
3. Re: [Facelets] XHTML parse error when RichFaces filter in web.xml is specified
ilya_shaikovsky Jun 2, 2010 3:32 AM (in response to honyk)Can anybody confirm that RichFaces works properly in Facelets environment?
http://livedemo.exadel.com/richfaces-demo/welcome.jsf - JSF 1.2 vs facelets. Deployed on tomcat 5.5 but I've used Tomcat 6 durng development. And also checked that works under JSF 2.0. But in order to work with 2.0 - start with the http://community.jboss.org/wiki/RichFaces333andJSF20 document.
-
4. Re: [Facelets] XHTML parse error when RichFaces filter in web.xml is specified
honyk Jun 17, 2010 4:18 PM (in response to ilya_shaikovsky)I finally got it to work!
It is necessary to add the faces-config.xml file into the WEB-INF folder although in my case it consist of the root element only.
Regards,
Jan