Ajax4JSF vs IceFaces

[antispart]

I'm curious if Seam will be moving away from A4J towards Icefaces. I don't mean to state that support for the two is mutually exclusive - which it's not (to my knowledge). I ask only because I noticed the latest booking example was ported to Icefaces.

There is some overlap between the two in terms of functionality and I'm wondering what direction Seam will take or what preference Seam maintainers have.

I haven't be able to use Icefaces with JSF RI 1.2 -- and I believe someone linked a forum post on icefaces.org that stated that they're looking at Q1 07 for 1.2 compatibility. So, as much as I'd like to try out Icefaces I don't want to switch to 1.1 or myfaces right now.

Any thoughts?

[gavin.king]

I believe that both are excellent and with some additional maturity will both be really compelling solutions. I also strongly believe that the value of JSF is the *many* options that will be available, and the fact that you can safely use them together (currently you can't use both Ajax4JSF and icefaces in the same app, but that is just a matter of maturity).

So we will not be making a choice between these two products, we will continue to support both (assuming that both teams keep improving their products and remain committed to open source).

[smartbinary]

Regarding:

assuming that both teams keep improving their products and remain committed to open source

Isn't it the case that only ICEfaces is open source for *both* the framework and the rich component libraries? In other words, the Exadel RichFaces (aka VCP)
http://www.exadel.com/web/portal/products/VisualComponentPlatform
is a commercial product ...

where the ICEfaces rich component libraries are free/open-source
http://component-showcase.icefaces.org/component-showcase
?


Regards,

Todd