I'll never know if it was the right decision. JSF 1.2 or 2.0, and despite the risks there were just too many good things When I was planning my project in Q4 2009 I had to decide on going with
I guess it's more fun, you know the story. I'll hold a party the day I hear that PrimeFaces have a dedicated bug-fixĪnd testing team coz there's a lot more emphasis on new functionality, Working so that I can have aligned fixed table headers in a vertical scroll I was really just trying to get their datatable RichFaces people are interested in this and there's a post on the richfacesįorum with more information. I think the issue is jQuery compatibility, the There are interoperability problems between PrimeFaces and RichFaces, No schedule component at present although they plan to develop one, Have a minChars type back-off functionality and performed badly. Imagined in my wildest nightmares that following the release of MojarraĢ.0 on 9th Dec 2009 that 14 months down the line they wouldn't have aĪ couple of other observations I made were that they don't have a workingĪutocomplete at present, they suggested using rich:select which doesn't
#DIFFERENCE BETWEEN PRIMEFACES AND ICEFACES FULL#
I assume they're developers) but I wonder how full time they are. More developers (well, more people with 5000+ post count on the forum, The first point I'd make is that although they have I recently had another look at RichFaces which There sure is a lot of redundancy though! For many, PrimeFaces is the de-facto standard of JSF Component Libraries. Following is a graph generated by Google Trends comparing the popularity PrimeFaces with the competitors. I hope all of this competition makes for better components. Thousands of applications have been created with PrimeFaces, even competing products like IceFaces is powered by PrimeFaces. This probably will be a factor when people evaluate component libraries.ĭon't forget about OpenFaces either. There is also the issue of PrimeFaces' basic reference materal being controlled and users charged for it. It seems RichFaces was the leader with JSF 1.2 and maybe will regain dominance with JSF 2 soon - especially if PrimeFaces remains basically a one developer project and continues releasing unstable code. IceFaces requires you pay money to get their good components and they use a special framework which is questionnable. It is probably fair to say that PrimeFaces has been the preferred JSF 2 component library for a year or two now. Note that each component library usually adds a bunch of extras such as skins, which you probably won't want to have more than one of, and it just makes your project more complicated.Īs far as comparisions are concerned, here is a thread in JavaRanch about the topic:
Compatibility is better than it used to be and you might be able to mix and match a little depending on what you're trying to do.
As far as compatibility is concerned you're likely to run into issues so it is probably still best to choose a single library and stick with it.
0 kommentar(er)
