On Fri, 2006-01-13 at 14:01 -0500, Balunas, Jay wrote: > Hello all, > > I have been lurking for some time, and have been investigating JSF for a new > project at my company. Please forgive me is this has come up already - I did > search through several pages of archives and could not find a reference to > 1.2 support roadmaps > > Because this will be a new project starting in about a month, and first > release around end of summer (August -September) I have been investigating > both the current 1.1.1 version of myFaces, and looking into what 1.2 JSF > provides. We are planning on using Ajax and from what research I have done > JSF 1.2 has some hooks for making Ajax requests less of a hack into the life > cycle. > > We are also investigating Suns implementation, but I would prefer to stick > with myFaces as the support and community seems stronger.
Note that all the following is not "official"; I'm a myfaces committer, but not part of the project management committee. This info is just my view from what I observe happening... Firstly, the JSF 1.2 spec is not yet released; it's at "proposed final draft", and has been for many months. I doubt very much if MyFaces will manage to release a 1.2-compatible version in the next six months. Sun have made JSF 1.2 dependent on a new version of the EL "expression language" library, and on a new version of JSP. Until those exist MyFaces can't even begin to implement much of JSF 1.2. And I'm not aware of any progress on implementing the next JSP version by Apache Tomcat or other such projects. As far as I am aware, Sun is the only one with an implementation of this near completion. That would, in fact, prevent the official release of the spec for many organisations; it's common to require at least 2 successful implementations of a spec before it is considered ready for release. I'm not sure that Sun works by those rules though. MyFaces is intending to add some JSF1.2 type features into the current 1.1-compatible release. Encrypted client-side sessions are already done for example. In addition, there is still a lot of work to be done to stabilise the current 1.1-compatible release. I personally would like to see effort put into this before moving on to the next spec version. Regards, Simon
