RichFaces 4.0 is a JSF 2.0 framework for building Ajax-enabled Java web interfaces. DZone Refcard #138 is a free, practical introduction to its two tag libraries—a4j for Ajax behavior and rich for UI components—and to setup, validation, JavaScript APIs, skinning, and the Component Development Kit (CDK). It is best used as a quick orientation and lookup aid, with the Developer Guide as the deeper reference for implementation details.
What is RichFaces 4.0?
RichFaces 4.0 builds on JSF 2.0 to provide Ajax-enabled UI components and framework features such as dynamic resource support, skinning, and a component development kit. It extends JSF capabilities including built-in Ajax, Facelets, annotations, and view parameters.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Jsf 2 Na Pratica Com Richfaces | $25.71 | Buy on Amazon |
| 2 |
|
JSF 1.2 Components | $50.99 | Buy on Amazon |
| 3 |
|
JFK: The Book of the Film (Applause Books) | $17.37 | Buy on Amazon |
| 4 |
|
JSF2 and RichFaces4 use guidebook (Chinese edidion) Pinyin: JSF2 he RichFaces4 shi yong zhi nan | $36.37 | Buy on Amazon |
| 5 |
|
JBoss RichFaces 3.3 | $39.99 | Buy on Amazon |
DZone calls its publication RichFaces 4.0 — A Next Generation JSF Framework, Refcard #138. The listed authors are Nick Belaevski, Team Leader at Exadel; Max Katz, Program Director, Developer Advocacy at IBM; Jay Balunas, JBoss Seam QE Lead at JBoss; and Ilya Shaikouski, Principal Architect at Exadel.
What does the DZone refcard cover?
The refcard is a breadth-first guide: it introduces the framework’s main concepts and directs attention to the areas developers need to know, rather than replacing detailed component documentation.
#1 Best Overall
- Getting started with RichFaces 4.0 and its tag libraries
- Ajax processing and component behavior
- Validation, including client-side validation
- Client functions and the Rich Components JavaScript API
- Skinning
- The Component Development Kit (CDK)
- Google Application Engine support
The DZone refcard’s table of contents establishes that these subjects are covered, but it should not be treated as a complete specification for each component or integration. Use the RichFaces Developer Guide when you need the detailed rules for a particular tag or attribute.
How do a4j and rich tags differ?
a4j: Ajax and page-level behavior
The a4j library supplies core Ajax mechanisms and controls that affect how parts of a JSF view are processed and updated. Examples documented in the Developer Guide include a4j:commandButton, a4j:commandLink, a4j:poll, and a4j:ajax.
rich: ready-made UI components
The rich library provides self-contained rich components, such as calendars and trees. The libraries complement one another: rich supplies interface components, while a4j provides Ajax behavior and processing controls.
Rank #2
- Used Book in Good Condition
How do you start a RichFaces 4 application?
Check the JSF container
The DZone refcard describes RichFaces 4.0 as usable in JSF 2.0-compatible environments. Its examples include EE6-compliant application servers such as JBoss AS 6/7 and GlassFish 3, and servlet containers such as Tomcat and Jetty. These are historical compatibility examples from the RichFaces 4.0 documentation, not a statement about current server support.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChoose a dependency setup
For Maven, the refcard describes using the RichFaces BOM together with the richfaces-components-ui and richfaces-core-impl artifacts. The official Developer Guide also documents the richfaces-archetype-simpleapp Maven archetype. Consult the version-specific guide for the matching dependency coordinates and versions rather than assuming that a current Maven project can use RichFaces 4.0 unchanged.
For an Ant-style installation, the refcard lists the core and component libraries along with SAC, a CSS parser, and Guava jars. It does not call for a RichFaces 4.0 web.xml filter update.
Rank #3
Declare the tag libraries in XHTML
The Developer Guide gives these namespace declarations for views using the libraries:
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"With the dependencies available, declare the namespaces on the XHTML view and use tags from the appropriate library. The archetype is a documented starting point if you want a Maven-generated simple application structure.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →How do execute and render work?
In an Ajax request, execute determines which portion of the JSF component tree is processed; render determines which components are updated afterward. These are separate decisions: processing a component does not by itself mean that its output is refreshed in the browser.
Rank #4
The guide lists @all, @none, @this, @form, and @region as accepted values for both attributes, with possible component-specific additions. Choose the narrowest relevant processing and update targets for the interaction; check the component’s documentation for any additions or exceptions.
Keep a section updated across Ajax requests
An a4j:outputPanel with ajaxRendered="true" is documented as an always-updated section. The guide notes that rich:message and rich:messages use this behavior. Set limitRender="true" when a request should override that automatic rendering behavior.
How does RichFaces skinning work?
RichFaces skins provide a palette of font and color parameters that sit above ordinary CSS. The Developer Guide lists predefined skins including plain, emeraldTown, blueSky, wine, japanCherry, ruby, classic, and deepMarine.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBest Value
The active skin is selected through the org.richfaces.skin context parameter. Skins can also be changed at runtime. ECSS files map component styles to skin parameters, allowing component styling to draw on the shared palette rather than relying only on individual CSS rules.
Which RichFaces reference should you use?
| Resource | Format and cost | Best use | Version or status context |
|---|---|---|---|
| DZone Refcard #138, RichFaces 4.0 — A Next Generation JSF Framework | Free refcard | Quick orientation across setup, Ajax, validation, JavaScript, skinning, CDK, and Google Application Engine support | Specifically about RichFaces 4.0 |
| RichFaces Developer Guide | Developer documentation; cost not stated | Detailed setup, tag, Ajax-processing, and skinning behavior | Consult the guide corresponding to the RichFaces version in use |
| Practical RichFaces, by Max Katz and Ilya Shaikovski | Book; Springer lists softcover and PDF eBook purchase options | Book-length treatment of RichFaces 4, JSF, and Ajax | Apress second edition; 408 pages; softcover ISBN 978-1-4302-3449-4 |
The archived JBoss release center presents RichFaces 4.0 as an evolution for JSF 2.0, with goals including a simplified CDK, custom behaviors, and dynamic resource support. Its milestone plan anticipated 4.0.0.Final at the end of March 2011. That is historical release planning, not a current support commitment.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
