It has now been almost two years since the development of RichFaces ended, however since people are still using it I just want to clear up a few things.
The showcases were down earlier this year, I had to switch hosting and it didn't go as smoothly as expected. showcase.richfaces.org is now back up and should hopefully remain so for at least another year. Showcase for RF 3 is however not coming back, if you want to use it you will have to deploy it locally; it's just not feasible for me to get it up and running. I found out the demos that were hosted at exadel.com are now also down but I have no control over those.
As far as I know there are no plans to shut down the current "infrastructure" (JIRA, source repositories, this whole site). That said I do not recommend using the JIRA, I'm generally ignoring it. If you want to get a hold of me the forum is the best place to do it. You can also try the RichFaces Twitter but I don't check it that often.
That's about it. Should things change I'll post an update. If you have any questions ask in the comments.
RichFaces 4.5.17.Final is available for download.
Note that this is the last release of RichFaces and the project has now reached its end-of-life. Thank you for staying with us for the past years.
In this release we've implemented a way to disable items in select, pickList and orderingList. We've also fixed an issue with combining RichFaces ajax functionality with basic JSF components and fixed issues with JS API in several components.
RichFaces 4.5.16.Final is available for download.
In this release we have fixed the "resetValues" attribute not working with MyFaces and we've fixed minor bugs and improved several components such as select, pickList and fileUpload.
RichFaces 4.5.15.Final is available for download. This release contains mostly client-side fixes, we have fixed single selection in extendedDataTable and made the table remember scroll position between AJAX requests. We have also fixed autocomplete and progressbar to allow resizing.
RichFaces 4.5.14.Final is available for download.
In this release we've implemented a long-requested feature - a menu for hiding columns in rich:extendedDataTable (you can see it action in the Showcase). We've fixed ajax requests in rich:tree, rich:treeNode now inherits request-related attributes (oncomplete, data, …) from the parent tree. There were two updates that might cause issues with custom styles, the components affected are rich:contextMenu (style and styleClass now apply to a different element) and rich:popupPanel (style was being incorrectly applied in two places).
as you might be aware the RichFaces project is winding down. (You can read Brian’s original RichFaces 4.5 announcement here).
For now the plan is to keep doing what we’ve been doing, that is releasing a new version of RichFaces 4.5.x roughly every four weeks and that will continue until June 2016, after which we will not sponsor any more releases. I will still keep an eye on the forum and StackOverflow but I will not be doing any more coding for RichFaces.
As for the current situation - there are some 800 unresolved issues and that is a rather large number. On the other hand a lot of those issues are old and so there is a high possibility that they are either outdated or they have a workaround. But if you know about an old issue that you’d like to see fixed a good way to bring it to my attention would be to vote or comment on it. Unfortunately Feature Requests and Enhancements are likely to get rejected at this point.
I've also put together a Questions and Answers page that I'll be updating if you have any more questions.
If you are a Red Hat customer please take a look at a related product announcement.
RichFaces 4.5.13.Final is available for download.
In this release we have fixed an issue with client-side validation in iteration components, fixed a4j:ajax listening to rowclick event and fixed an issue with a4j:status becoming stuck in certain situations. We have also upgraded jQuery to the latest version (1.12).
RichFaces 4.5.12.Final is available for download.
In this release we have fixed a bug in rich:chart that prevented displaying sparse data sets and fixed a problem with nested elements inside rich:autocomplete (such as rich:placeholder). A "default node" functionality has been added to rich:tree, consult the showcase example to see how it works (part of this feature was already in place but largely undocumented).
RichFaces 4.5.11.Final is available for download.
In this release we have updated styling options for chart, notifyMessage and dataGrid and updated our VDL documentation with regards to default attribute values. We have also added an option to skip resource optimization during build (-Doptimization.skip)
RichFaces 4.5.10.Final is available for download.
The bulk of the updates in this release concerns the online Showcase. But we've also updated built-in filtering in dataTables - they can now be filtered by pressing Enter. We've also fixed JSF detection on WebSphere.
RichFaces 4.5.9.Final is available for download.
In this release we've added an option to use text-substitution in rich:contextMenu (more in documentation) and we've added focus() method to the JS API of input elements. We've also updated rich:componentControl to be able to use standard DOM methods.
RichFaces 4.5.8.Final is available for download.
In this release we've expanded the use of event handlers - oncomplete, onerror and status can be defined globally on a4j:queue. Added more commands to keyboard navigation for rich:calendar and fixed a few client-side issues such as row- and columnClasses in rich:extendedDataTable with frozen columns, or keyboard scrolling for pickList and orderingList.
Two things to note:
I've been recently made aware of a bug in the fileUpload component where the encoding of the filename would get corrupted during the upload. E.g. you can take a file named štěně.png (that's Czech for puppy) and after upload the name would be Å¡tÄ›nÄ›.png. It doesn't occur on servers that use Servlet 2.5 (e.g. JBoss EAP 6.4).
The issue is caused by a difference in default encoding between two standards:
When a request is sent to the server the headers may look like this:
A fileUpload request will look like this:
notice that the charset isn't specified, that's part of the XHR2 standard. When the request is parsed the server will use iso-8859-1 and the name gets corrupted.
Fortunately the default for HTTP can be changed, although if you change it to anything else than utf-8 - i.e. the encoding of the request - it will not work (we're getting this fixed in RichFaces 4.5.8).
<filter> <filter-name>SetCharacterEncoding</filter-name> <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> </init-param> </filter> <filter-mapping> <filter-name>SetCharacterEncoding</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
However this solution doesn't currently work on WildFly due to a bug in Undertow. The bug was reported and fixed, the fix will be available in the upcoming version. In the meantime if you encounter the issue you can fix the filename simply with
filename = new String(filename.getBytes("iso-8859-1"), "utf-8");
If you encounter an issue with the encoding after 4.5.8 is released please report it (if it's not on WildFly).
RichFaces 4.5.7.Final is available for download.
In this release we've fixed a bug with fileUpload causing error 413 in large forms and added support for begin, beforedomupdate and complete events. We've also addressed several client-side issues.
RichFaces 4.5.6.Final is available for download.
In this release we have enhanced file size handling for rich:fileUpload - you can now specify "maxFileSize" directly on the component and it will also serve to reject large files immediately on client-side. We've also added support for transparent color in custom skin properties.