views:

1215

answers:

4

I am using JSF 2.0 and I am looking for a copmponent library with minimal load in terms of performance. Which one is better to use if I have choice between RichFaces and PrimeFaces? What are the advantages and disadvantages of both?

+2  A: 

Both are cool. Richfaces is more developed and tested generally, since primefaces came out later than RF. Just have a look at the component showcase and choose the one you prefer.

Or even better, you can use both together, there are no compatibility problems.

The advantages is that you have a lot of components ready to use out-of-the-box. The disadvantage is that sometimes you don't have full control about what a component can or can't do (but you can always create your own component extending a library component), and that you have to load some libraries into the client side for them to work (make sense, but it decreases performance)

pakore
Well, Richfaces doesn't even have a JSF2-compatible release yet....
Gabor Kulcsar
RichFaces 4.0.0 Milestone 1 is Released!! , so start with that and grab the GA when it comes out
Bozho
Well, the milestone is missing many components. Only some are represented.
Odelya
+5  A: 

Currently Primefaces is the only component lib that I know of (for now) that has a complete JSF2 implementation. There are bugs and problems, and some components are to be rewritten, but development is lightning fast, the communication is excellent (I don't remember a single post on their support forum that hasn't been answered by Cagatay himself), and it is moving in the right direction (the new theming system is an example of that IMHO). I think Primefaces will be a mature JSF2 component lib by the end of the year.

There are some others, like Icefaces that I played with for a short time, but they are moving slowly and like I said, none of them are really JSF2 yet. Part of the reason for this is that Mojarra, the Sun reference implementation is quite buggy, and there some serious bugs that these component lib developers are waiting for to get fixed.

So my vote is definitely on Primefaces for now, we'll see how it will look like later.

Gabor Kulcsar
[OpenFaces](http://openfaces.org/) was also JSF2 ready for months, almost one year already like PrimeFaces. By the way, which Mojarra bugs specifically are they waiting for? I don't recall any serious bugs, so calling it "buggy" is a bit extreme.
BalusC
OpenFaces: from their homepage: OpenFaces 3.0 Early Access 1 dated 13 May 2010. I admit I did not evaluate it, so might be working well... but they still don't have an official release.Bugs: from the Icefaces blog: "During the ICEfaces 2.0 Alpha 2 development cycle the ICEfaces team had logged several important issues against Mojarra JSF 2.0.2 which were targeted to be fixed in the JSF 2.0.3 release." I remember one particular navigation bug which was a critical no-go for me... at least in Icefaces.
Gabor Kulcsar
I was targeting on OpenFaces 2.0. The 2.0 Early Access was released almost one year ago. The 2.0 went final about March this year.
BalusC
@BalusC - do you recommend using OpenFaces? Have you tried it? So far I only tried IceFaces (which I didn't like), PrimeFaces and RichFaces
Odelya
@Odelya: I haven't tried it. As far I've only used Tomahawk, PrimeFaces and Ajax4jsf (before it became an integrated part of RichFaces). That's also why there's no answer of me to this particular question :)
BalusC
+2  A: 

If you are evaluating PrimeFaces, following page would help;

http://www.primefaces.org/whyprimefaces.html

Cagatay Civici