Tuesday, January 20, 2015

RichFaces 4.5.2.Final Release Announcement

RichFaces

RichFaces 4.5.2.Final is now available for download! Check out @Michal Petrov's blog for the detailed RichFaces 4.5.2.Final release announcement.


Tuesday, December 2, 2014

RichFaces 4.5.1.Final Release Announcement

RichFaces

RichFaces 4.5.1.Final is now available for download! Check out @Michal Petrov's blog for details of what this 4.5.1.Final release includes.


Wednesday, October 29, 2014

RichFaces 4.5.0.Final Release Announcement

RichFaces

RichFaces 4.5.0.Final is now available for download! RichFaces 4.5 is a significant improvement over the previous 4.3 release, offering JSF 2.2 compatibility, new components, a simplified build and distribution layout, and Page Fragments for simplified functional testing. Please read below for details on each of these improvements..

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.5.0.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Compatibility with RichFaces 4.3: RichFaces 4.5 is intended to be backwards compatibility with RichFaces 4.3 and should be a drop in replacement into your applications, requiring only changes in your pom.xml.

Any breaking changes with RichFaces 4.5 are being tracked in our GitHub wiki migration page. Please update that wiki page with a Pull Request if you find any incompatibilities.

JSF 2.2 Compatibility

RichFaces 4.5 has been developed and tested against both JSF 2.1 and 2.2. Go forth and take advantage of the new features available in JSF 2.2.

Chart components

Thanks to the hard work of our Google Summer of Code student and subsequent intern Lukas Macko, we are providing a set of Chart components in RichFaces 4.5. Use these components to graphically represent the data in your applications with a similar API as the rest of your JSF components.

Read more about the RichFaces 4.5 charts in Michal Petrov’s blog post on using charts.

Component improvements

A number of existing components have seen some improvements in RichFaces 4.5. These are outlined below:

Select component with autocomplete

The <rich:select> component has been augmented to support the same auto-completing functionality as the <rich:autocomplete> component. The rule-of-thumb to keep in mind when deciding between incorporating either of these similar components is as follows:

  • use the <rich:select> component when auto-completing a list of backend objects.

  • use the <rich:autocomplete> component when auto-completing with text-based input.

Built-in sorting and filtering of the DataTable

The <rich:dataTable> has picked up the built-in sorting and filtering capabilities that have been available for some time in it’s big brother the <rich:extendedDataTable>.

If you are already using the <rich:dataTable> in your application with custom controls, and do not wish to take advantage of the built-in controls, then please refer to the Component reference for instructions on disabling the builtin sorting and filtering controls.

Push with web-sockets

We’ve upgraded our atmosphere dependency to version 2.2, allowing our <a4j:push> component to take advantage of web-sockets. The component will gracefully fall-back to long-polling when web-sockets are not available in either your deployment container nor in the browser.

Fileupload

The <rich:fileupload> component has been re-worked to take advantage of the new APIs provided with the Servlet 3.0 specification. This re-implementation has allowed us to add some new features. Check out the Fileupload sample in the showcase to play with the new implementation.

Under the hood

A number of improvements have been made in RichFaces 4.5 under the hood, these include:

A new ExtendedPartialViewContext

The new RichFaces EPVC extends the PVC in Mojarra, rather than fork it. This has the effect of not only making our EPVC easier to maintain with new Mojarra releases, but also eases compatibility with other JSF libraries.

However, due to a patched bug in Mojarra, our new EPVC will only work with newer Mojarra releases. As such we’ve implemented a check verifying that you are running in a container providing Mojarra ≥ 2.1.28 or ≥ 2.2.6. MyFaces is not affected by this bug.

Simplified build

The build in RichFaces 4.5 has been greatly simplified. We’ve consolidated the RichFaces source down to a single github repository. Along with improvements to the CDK, we have been able to drastically reduce our developer turnaround time when working with the framework.

It’s also expected that this simpler build structure will encourage more community contributions, so get those Pull Requests coming!

Page Fragments

If you do functional testing (or would like to) and haven’t yet looked at the Arquillian Graphene Page Fragments, then do yourself a favour and do so.

This is all the more relevant with our RichFaces 4.5.0.Final release as our RichFaces QE team has ported their set of page fragments for RichFaces components to the framework, providing you with a stable set of page fragments matching the shipped components. Write your tests to the stable page fragments API, and you won’t be caught by surprise with failing tests when the DOM implementation of a component changes in a future release.

Have a look at one of our Framework tests to see these page fragments in action.

Asciidoc

We’ve ported the RichFaces docs from the hard-to-work-with docbook xml to the writer’s paradise that is Asciidoc. This migration was motivated in large part by the Asciidoc improvements introduced by the Asciidoctor team. Thanks guys!

The docs are on github and ready for pull requests!

Release Notes

Check out the Release notes for a list of the issues addressed since the 4.5.0.CR2 release.

A bug with Mojarra

An unfortunate regression in Mojarra caused by the fix to JAVASERVERFACES-3152 has broken a number of RichFaces components when nested in a <ui:repeat> component (see RFPL-3506). We are working with the Mojarra team to see this resolved (via JAVASERVERFACES-3452).

In the mean time please use the <a4j:repeat> component as a workaround.

Next steps

We will follow on the 4.5.0.Final release with a series of micro releases further improving the stability of our framework. There are no planned additional releases of the 4.3 branch.


Tuesday, May 27, 2014

RichFaces 4.3.7.Final Release Announcement

RichFaces

The RichFaces stable branch receives an update with the release of RichFaces 4.3.7.Final. This most recent micro release of the RichFaces 4.3 release series provides a number of bug fixes while we concurrently work on getting a JSF 2.2 compatible RichFaces 4.5 released.

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.7.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Release Highlights

This release resolves 13 issues, making RichFaces 4.3.5 a small bug-fix release. Hopefully this reflects well on the stability of the framework! The issues themselves address fixes for the tab, popupPanel, push, contextMenu, pickList and showcase. Full details of the fixes included are available in the release notes below.

Bug

  • RF-11417 - Tab: investigate why @action does not work

  • RF-11427 - rich:tab - actionListener

  • RF-11736 - rich:popupPanel x domElementAttachment="parent"

  • RF-13569 - Photoalbum: the change of users avatar doesn’t work

  • RF-13592 - a4j:push doesn’t work after rendering

  • RF-13613 - ContextMenu doesn’t show on mouseover

  • RF-13616 - PopupPanel autosize with togglePanel doesn’t resize

  • RF-13629 - popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true

Component Upgrade

  • RF-13364 - Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x

Enhancement

  • RF-13478 - VDL documentation typos

  • RF-13506 - Incorrect information on showcase fileUpload sample page (maxRequestSize description)

  • RF-13564 - rich:pickList shows an outline when clicked

Task

  • RF-13512 - Photoalbum: port fix from RF-13498 to RF4 photoalbum

Moving forward

We are finishing off work on our RichFaces 4.5 release to address JSF 2.2 compatibility with the RichFaces 4.x branch. This has necessitated we put RichFaces 5 development on hold, but we feel will be worth it to get JSF 2.2 support in a stable release sooner rather than later.


Monday, January 27, 2014

RichFaces 4.3.5.Final Release Announcement

RichFaces

We are happy to release an update to our stable branch with the release of RichFaces 4.3.5.Final. This 5th micro release of the RichFaces 4.3 release series provides a number of bug fixes while we concurrently work on RichFaces 5.

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.5.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Release Highlights

This release resolves 50 issues, making RichFaces 4.3.5 a substantial bug-fix release. The issues themselves span a number of components and features, offering an overall increase in framework stability.

With this release we have brought back the Photoalbum demo from the RichFaces 3 project. We’ve enhanced the demo offering social media tie-ins to facebook and google plus. Check out the source code on github.

Bug

  • RF-11469 - autocomplete method does not resolve bean if ui:included and only one parameter provided

  • RF-11973 - rich:contextMenu - after ajax re-render of table contextMenu no longer works

  • RF-12811 - VDL Documentation: rich:calendar is missing attribute "maxlength"

  • RF-12813 - rich:panelMenuItem executes action even if disabled attribute evaluates to true

  • RF-13172 - rich:toolbarGroup location="right" doesn’t work if toolbarGroup location="left" contains not rendered values

  • RF-13208 - Push: error "not well-formed" appears in browser console in Firefox - make messages a valid XML

  • RF-13220 - Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts

  • RF-13239 - Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x

  • RF-13252 - a4j:ajax includes jsf.js script twice

  • RF-13257 - PhotoAlbum: uploading and deleting images

  • RF-13266 - mediaOutput not working anymore on Glassfish3 and EAP6.1

  • RF-13287 - rich:extendedDataTable column resizing with ajax loading not working properly

  • RF-13292 - Autocomplete: up and down arrow keys not working in Opera

  • RF-13298 - Richfaces BOM manages a non Maven Central dependency

  • RF-13342 - archetype-simpleapp: facelet with name title is not defined in template, but it is used in the sample

  • RF-13358 - rich:panelMenuGroup allowing actions executions even if originally disabled

  • RF-13455 - The rich:tabPanel no longer visits tab header facets while rendering a response.

  • RF-13464 - Photoalbum: bad positioning of progressBar for G+/FB login on Firefox

  • RF-13465 - Photoalbum: cannot run album slideshow when an image has been added

  • RF-13466 - Photoalbum: editor for creating comments has not visible toolbar

  • RF-13467 - Photoalbum: wrong selector in js function when selecting album from multiple album groups

  • RF-13468 - Photoalbum build fails with JDK 6

  • RF-13471 - Photoalbum: search: option for search in own albums is not visible when logged in

  • RF-13473 - Photoalbum: cannot open help for fileUpload and dataScroller

  • RF-13485 - Photoalbum: cannot login with FB account

  • RF-13486 - Photoalbum: viewing g+ albums improvements

  • RF-13487 - Photoalbum: viewing FB albums improvements

  • RF-13497 - Photoalbum: cannot add album via contextMenu

  • RF-13500 - Photoalbum: viewing Facebook albums throws exception

  • RF-13501 - PhotoAlbum: sharing a photo does not work, can not choose album

  • RF-13502 - Photoalbum: editing uploaded photo throws NPE

Component Upgrade

  • RF-13277 - Upgrade Atmosphere to 1.0.18

  • RF-13310 - Upgrade Graphene and Warp in 4.3 branch Enhancement

  • RF-13274 - Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart

  • RF-13314 - Deprecate reslib resource files

  • RF-13439 - Photoalbum - update help section

  • RF-13462 - Photoalbum: improvements for adding album and album groups

  • RF-13463 - Photoalbum: improvements for adding images

  • RF-13479 - Re-organize files/folders in the top-level webapp folder

  • RF-13480 - Java package re-structure for the photoalbum demo

Epic

  • RF-13047 - Implement improvements to the photoalbum application

Feature Request

  • RF-12793 - Photoalbum improvements

  • RF-12949 - Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works

  • RF-13227 - Prepare the RichFaces 4.3.x photoalbum for release

  • RF-13305 - Autocomplete: i must press button twice for popup window

  • RF-13306 - Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))

Patch

  • RF-13268 - Typo in LookAheadObjectInputStream.java Task

  • RF-13404 - Port the RichFaces 5 improvements back to RichFaces 4.3

  • RF-13405 - Merge the photoalbum fixes from QE

  • RF-13509 - Add Photoalbum sources to RichFaces distribution

Moving forward

You will likely have noticed no mention of JSF 2.2 in this announcement. We are not at this time introducing JSF 2.2 support into our stable branch, but are rather doing so in the upcoming 5.0.0.Alpha3 release of RichFaces. Progress on RichFaces 5 has continued while we prepared the 4.3.5 release, and we have already committed a number of JSF 2.2 related fixes. Look for this release in the next week or two.


Tuesday, September 17, 2013

RichFaces 4.3.4.Final Release Announcement

RichFaces

I am excited to announce the release of RichFaces 4.3.4.Final. This 4th minor release of the RichFaces 4.3 release series is conservative in scope focusing on providing bug fixes to our stable release branch while we concurrently work on RichFaces 5.

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.4.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Release Highlights

With 47 issues resolved, RichFaces 4.3.4 is a substantial bug-fix release, offering improvements in a number of components including the select components, extendedDataTable, popup panels, and a4j:log.

Additionally we upgraded our Atmosphere dependency to the latest release (1.0.17) to ensure RichFaces Push continues to work with the upcoming JBoss EAP 6.1.1 release. A big shout out to @jfarcand and his Atmosphere community for accepting our pull request and getting an updated release out in a timely manner. Working with Atmosphere as an upstream project is truly an example of OSS at it’s best!

Bug

  • RF-11275 - showcase - rich:popup - Sample Modal panel - after changing the size of popup there is double shadow

  • RF-11691 - [rich:select] value disappears if you click between list and value

  • RF-12345 - JS error when pressing ESC on an open inplaceSelect in IE

  • RF-12853 - rich:inplaceSelect: JS API bugs

  • RF-12929 - PickList change event not firing correctly when ordering objects in target area

  • RF-12943 - ExtendedDataTable: clearing of filter input doesnt work correctly

  • RF-12989 - Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final

  • RF-13010 - Popup panel inside popup panel: button not rendered in IE10

  • RF-13017 - richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible

  • RF-13035 - Simpleapp Archetype: mobile version shows modal dialog

  • RF-13046 - EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT

  • RF-13053 - Showcase: push doesn’t work on EAP 6.1

  • RF-13057 - Kitchensink Archetype: update enterprise version of JBoss BOM

  • RF-13058 - Kitchensink Archetype: JSF community site link doesn’t work

  • RF-13059 - Richfaces quickstart README files contain links that to be updated

  • RF-13060 - Issue in initializing the list of selected items in a Picklist

  • RF-13086 - Popup panel: button’s label is invisible in IE8

  • RF-13094 - Wrong extendedDataTable header widths when narrowing columns

  • RF-13098 - Regression: mediaOutput broken for CDI MediaData beans

  • RF-13102 - rich:calendar with date pattern- input gets cleared on click

  • RF-13106 - Quickstart names in the POM files are not consistent and often are not clear

  • RF-13107 - ajaxRenderer component are renderer even though they are in non-active switchable panel, causing JSF to fail to update DOM

  • RF-13117 - ExtendedDataTable Sorting resets $(window).resize Events

  • RF-13119 - kitchensink-rf test-ds.xml does not use a unique datasource JNDI name

  • RF-13125 - a4j:log swallows the message from jsf.js’s sendError method

  • RF-13133 - ExtendedDataTable: filterType=custom doesn’t work when mixing custom and built-in filter columns

  • RF-13136 - a4j:log with mode=console doesn’t take log level into consideration

  • RF-13137 - a4j:log - wrong log levels in attribute description

  • RF-13140 - PopupPanel: Hide @visualOptions and @keepVisualState options which weren’t implemented yet

  • RF-13142 - Showcase: mediaOutput sample is not working with MyFaces

  • RF-13149 - a4j:push in Metamer doesn’t have subtopic name

  • RF-13161 - rich:notifyMessages CSS incorrect on MyFaces 2.x

  • RF-13174 - Correct the WFK version of the JBoss BOM used in the archetypes

  • RF-13195 - Showcase: Unauthorized deserialization attempt with MyFaces

  • RF-13205 - Photoalbum: Hibernate error during deployment

Component Upgrade

  • RF-13132 - Upgrade JBoss Java EE BOMs to 3.0.2.Final

  • RF-13154 - Upgrade Atmosphere to 1.0.17 (a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6) Enhancement

  • RF-12784 - Showcase readme - update deployment from eclipse part

  • RF-13097 - showcase: update readme with password for jbas7 profile

  • RF-13150 - Remove JMS functionality from the RichFaces showcase

  • RF-13153 - Update version.compiler.plugin and jboss.maven.plugin versions in the quickstart POM files

  • RF-13169 - Replace hardcoded version in Arquilian FundamentalTestConfiguration with project version property - from pom file

Feature Request

  • RF-13038 - Command button/link: attribute tabindex missing

  • RF-13063 - RichFacesInputNumberSlider setValueByDragging

  • RF-13159 - Add Maven compiler properties and remove Maven plugin from the the quickstart POM files

  • RF-13185 - Quickstarts: Modify GAV to use org.jboss.quickstarts.rf

Sub-task

  • RF-13189 - Update jquery-atmosphere.js to 1.0.17 in 4.3.x

Moving forward

We are actively working on RichFaces 5.0.0.Alpha2 that will feature some re-worked components taking advantage of our new decoupled component architecture and making use of standalone javascript widgets to provide a more robust client-side implementation of RichFaces components. Look forward this a new Alpha release in the coming weeks.


Thursday, May 16, 2013

RichFaces 4.3.2.Final Release Announcement

RichFaces

I am excited to announce the release of RichFaces 4.3.2.Final. - This 2nd minor release of the RichFaces 4.3 release series provides a number of bug fixes further increasing the stability of the framework.

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.2.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Release Highlights

This release of the RichFaces framework is not accompanied by a release of the CDK. The 4.3.2.Final release of RichFaces was created with the 4.3.1.Final version of the RichFaces CDK. Future RichFaces 4 releases will only be accompanied by a RichFaces CDK release when a CDK fix was required to enable the framework release.

With fixes to the extendedDataTable, tab panel, autocomplete, fileuplaod and popup panel, as well as some fixes addressing compatibility with the latest Mojarra release, you’ll definitely want to move your applications to this release and take advantage of these improvements. Refer to the release notes below for a complete listing of what has been fixed in this release.

Bug

  • RF-12193 - rich:extendedDataTable is blank on show

  • RF-12765 - Rich:tabPanel not possible to switch tabs when only dynamic tabs are present

  • RF-12812 - Autocomplete does not hide popup on tabbing to the next field

  • RF-12827 - Showcase - switching among dynamically created panels, tabs cease to function

  • RF-12839 - Toggle panels: ajax-related attributes do not work

  • RF-12846 - a4j:commandLink accesskey attribute missing

  • RF-12847 - Fix quickstart license and white space issues exposed by qstool report

  • RF-12848 - Error "source is not defined" after richfaces-jsf-event.js merge

  • RF-12850 - Popup panel: button's label is invisible in IE10

  • RF-12851 - The RichFaces kitchensink-rf quickstart/archetype incorrectly depend on the AS google guava module

  • RF-12858 - rich:calendar dateselect event is fired twice

  • RF-12868 - Update the Summary of the RichFaces kitchensink quickstart

  • RF-12893 - Partial response not ended correctly on exception

  • RF-12928 - ExtendedDataTable: columnsOrder doesnt work after changing order

  • RF-12931 - rich:fileupload broken with jsf.js changes in Mojarra 2.1.21

  • RF-12933 - rich:tooltip replace 'defaultContent' facet in docs and examples with 'loading'

  • RF-12958 - Popup panel opened from inside popup panel doesn't work

  • RF-12969 - rich:tabPanel: Click on already selected rich:tab causes JavaScript error

  • RF-12975 - rich:extendedDataTable - can not change order of columns

Component Upgrade

  • RF-12688 - Upgrade Guava from 11.02 to 13.0.1

  • RF-12780 - Upgrade to Mojarra 2.1.19

  • RF-12898 - Tie RichFaces 4.3 to CDK 4.3.1.Final

Enhancement

  • RF-12784 - Showcase readme - update deployment from eclipse part

  • RF-12786 - Showcase - rewrite readme to markdown

  • RF-12964 - Create appropriate push timeouts for the showcase

Feature Request

  • RF-12810 - Introduce profiles for verification of fundamental tests on Tomcat 6 and 7, TomEE 1.5 and GlassFish 3.1

  • RF-12849 - Showcase - update readme - remove obsolete, add new

  • RF-12935 - Fix resolution of framework tests' artifacts with version enforced

  • RF-12937 - Introduce a profile for running framework tests against JBoss EAP

  • RF-12938 - Update Shrinkwrap

  • RF-12940 - Showcase: fix path to outputPanel - compositeMessages sample source

  • RF-12941 - Showcase: ProgressBar demo - remove obsolete attribute and make the progress smoother

Task

  • RF-12843 - Apply unix style line-endings to the entire codebase

Moving forward

We’ve finished development of RichFaces - 5.0.0.Alpha1, and our QA team is currently working on stabilizing for a release. So stay tuned for an exciting announcement of the availability of our first RichFaces 5 Alpha!


Thursday, October 18, 2012

RichFaces 4.2.3.Final Release Announcement

RichFaces

RichFaces 4.2.3.Final has been released. This Final release is a re-tag of the 4.2.3.CR1 release as no blocking issues were found by either our QE team, nor by the community.

The RichFaces 4.2.3.Final release is purely a bug-fix release, with a focus on compatibility between RichFaces and the JBoss Portlet Bridge. I’ll refer you to the RichFaces 4.2.3.CR1 release blog for details of the release, with a special highlight paid to the contributions from the JBoss Portal Bridge team, and contributions from community members.

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.2.3.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Release Notes:

To re-cap, the changes in the 4.2.3.Final release compared to the 4.2.2.Final release include:

Bug

  • [RF-10758] – Input fields in popupPanel lose focus
  • [RF-10980] – Impossible to set tabindex of input inside rich:popupPanel
  • [RF-11051] – a4j.version does not work
  • [RF-11104] – rich:inputNumberSlider slider position is affected by css position attribute of containing element
  • [RF-12113] – rich:inputNumberSpinner minValue and maxValue being ignored after second request
  • [RF-12114] – Richfaces 4.2 rich:autocomplete don't fire ajax on blur event
  • [RF-12221] – rich:orderingList: fix VDL-DOC of @listHeight, @maxListHeight, @minListHeight, @listWidth
  • [RF-12256] – DragAndDrop + position: absolute results in broken positioning
  • [RF-12273] – rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL
  • [RF-12424] – Showcase contains Servlet specific code
  • [RF-12425] – Showcase fails to load SyntaxHighlighter scripts when Require.js is present
  • [RF-12476] – Resource Name in mapping for two menu images is incorrect

Enhancement

  • [RF-12343] – Problem when saving form with rich picklist inside composite component

This is very much a community driven release. Thanks guys, you rock!

Stay Tuned for 4.3.0.M2

The QA process for the 4.3.0.M2 release is about to begin, with a release as soon as QA is done. So stay tuned, as there is lots more great stuff to come!


Tuesday, May 15, 2012

RichFaces 4.2.2.Final Release Announcement

RichFaces 4.2.2.Final is available, the second RichFaces 4.2 micro release. This release was originally intended to focus on changes required to better align with the upcoming JBoss AS 7.1.2 release. However we had some community members step forward with some fixes, and those contributions ended up turning this release into a reasonable bug fix release!

I would like to give a big shout out to Luca Nardelli, Adrian Gonzalez, and Jason Porter. These are RichFaces users who contributed back to the project with bug fixes and new features; improving the quality of the JSF component framework we all use to build applications on a daily basis. Three cheers for OSS, and our community contributors! If you would also like to get involved and contribute code to the project, check out our ContributorGettingStartedGuide wiki page!

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.2.2.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

What’s new with 4.2.2.Final?

The rich:tooltip has seen a number of improvements centered around changing the javascript implementation to use the RichFaces Javascript Service feature, and defer javascript loading until all components are rendered. Nice catch Luca! Specific issues resolved with this approach include:

  • [RF-10839] – tooltip: attachment using target not works if tooltip defined before the component to which it attaches.
  • [RF-11370] – rich:toolTip: targetted example causes NPE for some IDs
  • [RF-12198] – rich:tooltip does not work inside a4j:commandButton
  • [RF-12199] – rich:tooltip does not work inside h:graphicImage

For those migrating from RichFaces 3, Adrian has contributed improvements to the Xcss2Ecss conversion utility:

  • [RF-11994] – Xcss2EcssConverter error handling f:importResource
  • [RF-12010] – ecss hot reloading

A number of other fixes are seen with:

  • rich:dataTable and rich:extendedDataTable
  • validation and messages
  • dependency updates, matching changes in the upcoming JBoss AS 7.1.2 release

Lastly I’ll mention a simple feature, but one which I’m sure many will find useful. The a4j:log component has a new mode of operation, the console mode, allowing a4j:log messages to be output to the browser javascript error console.

What’s Next?

We’ll shortly begin our 4.3.0.M1 sprint which will focus on MyFaces compatibility issues and some CDK improvements in this first milestone. Concurrent to this, we will be working in the RichFaces Sandbox to deliver our next-generation component set. Should any of the above initiatives appeal to you, feel free to get involved, and help move the project forward!


Tuesday, April 17, 2012

RichFaces 4.2.1.Final Release Announcement

We’ve released RichFaces 4.2.1.Final – the first micro release for the 4.2 release train. Since the CR1 release we’ve primarily addressed bugs with the Richfaces showcase and the RichFaces archetypes. CR1 itself focused on bug fixes and stability improvements throughout the framework.

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.2.1.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

What’s in 4.2.1.Final?

One noteworthy issue to take note of:

  • [RF-11940] – Our ajax push component (a4j:push) was not receiving pushes from the server on Android devices. We identified a bug in the Atmosphere framework which powers our push technology, a bug which we fixed and pushed back upstream (OSS for the win!).

Be sure to check out the 4.2.1.CR1 release blog for a more complete picture of what we addressed with this micro release.

New with this release, we are once again deploying the showcase on new infrastructure. The OpenShift Express service has been unified with OpenShift Flex to deliver a single service now simply referred to as OpenShift (see this FAQ entry). The end result for us is a simplified deployment and management console, and an easier ability to host multiple applications.

Moving Forward

We’re currently focused on improving the JSF testing and RichFaces mobile stories. However we’ll shortly begin our 4.3.0.M1 sprint which will focus on MyFaces compatibility issues. Concurrent to all this, we will working in the RichFaces Sandbox to deliver our next-generation component set. Should any of the above initiatives appeal to you, feel free to get involved and help move the project forward!