Live blogging from TheServerSide Symposium on the final day, attending “Ajax Applications with JSF 2 and New RichFaces 4” presented by Max Katz. Max is presenting a talk on Ajax, which has been added to JSF2, as well as integratin with RichFaces 4. Max will be part of a client-side panel in the next set of talks with myself, Cameron McKenzie, and Bear Bibeault in the main ballroom.
Attendance has been significantly reduced today as many people, CodeRanch staff included, have started flying back home.
1. JSF2 New Features
Max lists some of the new features in JSF2:
- Facelets
- Compsitie components
- Implicit Navigation
- Bean validation
- Basic Ajax – Focus of the talk
2. Ajax Support
Ajax support in JSF2 has been added via f:ajax tag. Max presents some code examples that include event handling for the Ajax tags.
3. Where are the rich JSF2 components?
Max focusses on JSF2 as a framework for developing extensive widgets and rich UI, but does not provide them. In other words, to use JSF2 in practice, you will need to also include a rich framework, built on top of JSF2, as part of your application. The rest of his talk is focussed on RichFaces 4, a rich JSF2 framework with customizable/skinnable widgets.
4. RichFaces 4
RichFaces 4 has basic support for JSF2, so it is the first cross-over transition. The CR1 is available and the main release is slated for the end of March or early April, so as soon as 1-2 weeks. The RichFaces 4 tag is available via a4j:ajax.
5. What’s new in RichFaces 4?
New version relies entirely on jQuery in JavaScript. Redesign for semantic HTML principles. Also includes server-side and client-side performance optimizations. Finally, a lot of code clean-up and review was completed by the RichFaces team.
From a deployment perspective, it supports publishing to Google App Engine as well as Amazon EC2 Cloud.
Conclusion
Max spent the rest of his talk presenting individual facets of the RichFaces 4 API. It was a little dry if you don’t have a strong foundation in RichFaces, but still educational. The client side valdation, based on bean validation, looked particularly useful.