The first candidate release of RichFaces 4.3 (4.3.0.CR1) has been released. This release candidate for the RichFaces 4.3 release doesn’t add any new features, rather it polishes, documents, and showcases the many new features added in the earlier 4.3 milestones (4.3.0.M3, 4.3.0.M2, 4.3.0.M1).

div(alert alert-info). To try out this release: You can download the distribution directly, or for maven users, increment the RichFaces version in your pom.xml to 4.3.0.CR1. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Documentation updates

If you are interested in taking advantage of some of the new feature additions described in the earlier milestone release blogs, be sure to check out the updated RichFaces 4.3.0.CR1 documentation, and the showcase snapshot which demos the latest updates to the showcase.

Some of the documentation highlights include:

• Component reference documentation for <rich:focus>
• Component reference documentation for <rich:placeholder>
• Built-in sorting documentation for the <rich:externdedDataTable>
• Built-in filtering documentation for the <rich:externdedDataTable>

Also, check out the code samples in the showcase:

• Code sample for <rich:focus>
• Code sample for <rich:placeholder>
• Code sample for built-in sorting and filtering with the <rich:externdedDataTable>

Bug fixes

Most of the bug fixes in CR1 centered around the new 4.3 features. These bug fixes include:

Validation fixes

• RF-12700 - LongRangeValidator client-side messages differs from server-side ones on MyFaces
• RF-12669 - Autocomplete: client side validation for custom validators doesn’t work

Select component fixes

• RF-12608 - pickList without collectionType results in failure to lazily load
• RF-12692 - rich:select - unknown validator SelectLabelValueValidator

New component fixes

• RF-12650 - rich:placeholder: when @rendered=false the placeholder is still rendered
• RF-12668 - rich:focus - stops to work when containing form is re-rendered by another form

• Iteration component fixes
• RF-12662 - Showcase - rich:extendedDataTable - Built-in sorting and filtering - ELException when text filter value provided instead of expected numbers
• RF-12691 - extendedDataTable: Header facet render problem in RichFaces 4
• RF-12672 - Collapsible sub table: noData facet doesn’t work inside switchable panels
• RF-12673 - Collapsible sub table: filtering doesn’t work inside switchable panels
• RF-12684 - The last page shows rows from the page before if rich:collapsibleSubTable is included in rich:dataTable with rich:dataScroller.
• RF-12714 - Showcase and rich:dataTable: sorting in Arrangeable demo doesn’t work

JSF compatibility fixes

• RF-12670 - JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
• RF-12693 - Mojarra fails to encode form inputs correctly when they doesn’t have name attribute

Drag and drop fixes

• RF-12666 - Showcase - Drag and Drop with indicator - the styles do not apply for indicator when dragging over various targets
• RF-12671 - dropTarget does not work inside dynamic tabs when switchType is ajax or server
• RF-12703 - showcase - drag and drop - JS error with default dragIndicator

Input fixes

• RF-11067 - rich:autocomplete popups with suggestions does not reflect the value in input
• RF-11565 - Showcase: multiple selections in rich:autocomplete doesn’t work when ‘clicking’ is used
• RF-12707 - rich:calendar - setValue(…) method from javascript API doesn’t work correctly

Misc fixes

• RF-12708 - rich:jQuery: wrong VDL documentation of selector attribute
• RF-12716 - VDL-doc for a4j:ajax incorrectly states that the listener method cannot accept parameters
• RF-12709 - richfaces.js: fire ajaxcomplete event
• RF-12705 - vdl documentation for a4j:outputPanel contains non-implemented layout=“none"
• RF-12713 - Listeners don’t work inside panels

Moving forward

We’ll let RichFaces 4.3.0.CR1 bake in the community for a few weeks. Take it for a spin, and report any regressions you should come across that our top-notch QE team might have overlooked. Hopefully we can have a final release out by the end of the month.