1 Reply Latest reply on Feb 6, 2010 8:20 AM by Nick Belaevski

    Richfaces seems great, but with some serious problems.

    x L Newbie

      I have been using JSF for while, and choose richfaces as our ajax framework. After first several months practices, I loved the richfaces. i found out many good reasons to use ricfaces. however now i consider to give it up. there are some reasons why i do this.

       

      1. performance issues, richfaces has some performance issues.

           for example, simple page load by jsf only use 4ms, but with a4jFilter, it will take 10-20ms(not modify any content).

           Some code in org.ajax4jsf.Filter is slow, like HtmlParser, even using FastHtmlparser.  normally will take 10 ms or more.

           do we really need to correct response output? I wrote my own html parser,  only use 0-1 ms.

       

      2. UI issues,  richfaces components have good looking. but slow speed. too many javascript loading, more worse we cant control this.

           do we really need complex ui effects with jsf component ? i dont think so, please left this part to other javascript frameworks, like  jquery. we use and test them more easily.

       

      3. jsf, ajax not are separated clearly.

           when we do complex functions in html, we need total control javascript, ajax. but in richfaces, we have to config many ajax properties in jsf component, which cant config in javascript. its bring us a lot of troubles. 

       

       

      jsf bring component mechanism to us, but also bring us complex under-layer. tuning jsf performance already take our a lot of time. we are looking for some jsf-ajax framework have clear boundaries between jsf, ajax, javascript.

      1. using javascript to control ui effects.

      2. total control ajax using javacript.

      3. server side states to jsf.

       

      thanks.

      Mark

       

      xihanlee@gmail.com

        • 1. Re: Richfaces seems great, but with some serious problems.
          Nick Belaevski Master
          Hi Mark,

          I have been using JSF for while, and choose richfaces as our ajax framework. After first several months practices, I loved the richfaces. i found out many good reasons to use ricfaces. however now i consider to give it up. there are some reasons why i do this.

           

          1. performance issues, richfaces has some performance issues.

               for example, simple page load by jsf only use 4ms, but with a4jFilter, it will take 10-20ms(not modify any content).

               Some code in org.ajax4jsf.Filter is slow, like HtmlParser, even using FastHtmlparser.  normally will take 10 ms or more.

               do we really need to correct response output? I wrote my own html parser,  only use 0-1 ms.

          Try switching off resources loading and check with FastHtmlParser. This should improve performance.

           

          2. UI issues,  richfaces components have good looking. but slow speed. too many javascript loading, more worse we cant control this.

               do we really need complex ui effects with jsf component ? i dont think so, please left this part to other javascript frameworks, like  jquery. we use and test them more easily.

          What UI effects do you mean?

           

          3. jsf, ajax not are separated clearly.

           

          when we do complex functions in html, we need total control javascript, ajax. but in richfaces, we have to config many ajax properties in jsf component, which cant config in javascript. its bring us a lot of troubles.

           

          Sorry, but I'm not getting your point. There are JSF components with built-in AJAX and you can easily create your own component that will provide as much control as you need and that's via JavaScript. Are there some problems with this?