You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Kito Mann <ki...@virtua.com> on 2012/06/02 01:22:01 UTC

ANNOUNCE: Brian Leathem reveals RichFaces 4.2 and discusses SeamFaces

I am pleased to announce a new Podcast withBrian Leathem -

JSFCentral Episode #26: Brian Leathem reveals RichFaces 4.2 and discusses
SeamFaces



In this podcast, JSFCentral editor-in-chief Kito D. Mann talks with Brian
Leathem about RichFaces and the Seam Faces Module.





 Here is an excerpt:



Kito

Yeah. Cool. Well, I wanted to talk about a couple things here today, which
relate to what you do. So, let's start out with updating people about
RichFaces, I know you guys are releasing RichFaces 4.2 right now. I think
CR1 came out on the 8th. And by the time you hear this, 4.2 will probably
be final.

And I think what I'd like to do is..RichFaces has a very long history,
started out as a product with Exadel and then has been with JBoss for quite
a few years now.

And I was just wondering if you could kind of give us an overview of what
happened with RichFaces 4.0 because that was the last sort of major
release. And I think a lot of people have worked with 3.x or have seen an
older version of RichFaces, and may not be kind of familiar with the
changes in 4.0. So, why don't we start with that, and then we can talk a
little bit more about the newer releases, especially 4.2.

Brian

Sure. Sounds good. So, RichFaces 4.0 was primarily focused on supporting
JSF 2.0. So with JSF 2.0, of course, we saw the standardization of the Ajax
approach in JSF, and a corresponding change in a number of the APIs that
component developers used to build components. So, with RichFaces 4.0 we
ported a number of the RichFaces 3.0 components to work with JSF 2.0 and
allow application developers to make a smooth transition from RichFaces 3.0
to RichFaces 4.0.

And along with that, we have a couple new features that we introduced with
RichFaces 4.0. We have the client side validation feature, which brings
bean validation into the browser with a JavaScript implementation. So, you
can get feedback-users can get feedback on validation errors right within
their browser. And similarly, we introduced the push feature with RichFaces
4.0 based on the Atmosphere Framework.







Read the full Podcast here:



http://www.jsfcentral.com/articles/leathem-05-12.html

JSFCentral Episode #26: Brian Leathem reveals RichFaces 4.2 and discusses
SeamFaces


-- 
___

Kito D. Mann | twitter: kito99 | Author, JSF in Action
Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter:
jsfcentral
+1 203-404-4848 x246

* Listen to the latest headlines in the JSF and Java EE newscast:
http://blogs.jsfcentral.com/roller/editorsdesk/category/JSF+and+Java+EE+Newscast
* Sign up for the JSFCentral newsletter: http://oi.vresp.com/?fid=ac048d0e17