I can't find it at the moment but this question was asked some time before and the answer was: No, you can't combine Richfaces and Icefaces.
By the way, why do you want to do that? If there is a very important thing icefaces is able to and richfaces is not, that could be something for the richfaces requested feature list. At least your problem is solved in the long term then. If not: use only richfaces :)
Well the problem is that icefaces has some extra features which some people here would want. So I would need icefaces.
I personally am not such a fan of icefaces and I do like very much the a4j support tag. So... I would also need richfaces.
Anyway, some bugs that arose with us using richfaces have made it hard for me to defend it.
I would generally think that for the sake of richfaces and basically all the JSF community that Red Hat should speed up development considerably. The reality is that JSF with its current component set it hardly at the level of asp.net 1.0 , and we all know at what version they have come already.
as I am evaluating different JSF Ajax frameworks, I would like to know the bugs you encountered in richfaces. Can you be more concrete about it?
It would help me alot. Thanks.
Well there is a problem with the tab control when you use Facelets and want to use a valueChangeListener on it. That simply won't work. I am not sure how it is with other frameworks but but I find it very inconvenient that the behaviour can actually break when using Facelets.
I have also read some impressions on this forum from people who have used richfaces recently who weren't too happy with bugs. I can understand that a lot of new features were introduced with 3.1.0 but care should be taken. As I mentioned before, the succes of JSF will greatly depend on its components and JBoss now has the right base to push it forward! 2 developers (or something) might not be enough to do that.
A huge pro for rich / a4j is obviously the simple a4j:support, a4j:status tags and its compatibility with tomahawk (if you would like to use that too).
Furthermore (maybe wandering off a bit), and I'm talking in general now as icefaces doesn't have what we want either, but we are looking for a datascroller to enable paging in a datatable without having to retrieve all data records. In fact we have in our backend 10 records and the total number. It would be great if a special datascroller could support such behaviour that with a simple listener we could get the next 10 records and so on...
Adding to that... because of compatibility with other component libraries we will likely opt for richfaces because it makes us less vendor dependent.
I second that
No, you can't combine Richfaces and Icefaces.
I like this :)
The reality is that JSF with its current component set it hardly at the level of asp.net 1.0 , and we all know at what version they have come already.
At first, thanks for the information, Tomba.
I am looking for the exact same datascroller.
I am wondering why richfaces only has "fake" datascrolling. What is the sence of loading the whole data on the first page load, when you have a pageable table...
Well but I gonna dig deeper into that and hopefully I can manage to realize "real" datascrolling with richfaces... I will find out