1 Reply Latest reply on Feb 23, 2010 5:26 PM by Jay Balunas

    RF333. for JSF 2 is not compatible wiht JSF 2

    adam kanicki Newbie

      I spent a lot of time to test RF in action. Unfortunately you can't say it is compatible wiht JSF 2. Sure it works with Seam but not works with any other component library based on JSF 2. When I done all configuration based on richfaces-demo-jsf2-3.3.3.CR1-tomcat6.war it works correctly. But when I added other library like PrettyFaces or PrimeFaces it not works.


      In my opinion the problem is based on configuration and usage of faceltes 1.1.5. When you use this version of facelets any other components based on JSF 2 stops working. I have tried in many way and configuration on Tomcat and GlassFish but without efect.


      So I can say at this moment RichFaces3.3.3 is completely useless in the context of JSF 2.  CMS I have been working on is based mainly on RichFaces, but there is a huge drawback in JSF 1.2 specification. You can't set component id with ELexpression. In JSF 2 you can do that. But there isn't RichFaces compatible with JSF 2. So l looking forward in hope for RichFaces 4...

        • 1. Re: RF333. for JSF 2 is not compatible wiht JSF 2
          Jay Balunas Master

          Hi Adam,


          I'm sorry you have had so much trouble with 3.3.3 and JSF 2.  We have always meant the 3.3.3 to be a stepping stone for JSF 2 support, and as I said in my blogs ( 3.3.3.BETA1 and 3.3.3.CR1 ) and pointed to in the RichFaces 3.3.3 and JSF 2.0there are some limitations to the support that was possible in RichFaces 3.3.3.


          One of these is the built in facelets support in JSF 2.0.  We needed to make a trade off in between retro-fitting 3.3.X completely for JSF 2.0 ( a major undertaking ), or have limited JSF 2.0 support in 3.3.X and push forward with RichFaces 4.0 where we can really make great changes to get the most out of JSF 2.0.  We realize that this is a problem for new development and part of the reason that we are working so hard to get RichFaces 4.0 out.


          The goal of the JSF 2.0 support in RichFaces 3.3.3 is that you can run your existing RichFaces 3.3.X / JSF 1.2 applications in a JSF 2.0 / EE6 environment.  New development taking advantage of all of JSF 2.0 features with RichFaces will need to wait for 4.0.  The good news is that we are well on our way to our next 4.0 release, and will have several milestone releases to start your development with.