Chapter 4. The RichFaces Migration Issues 3.1.x
The RichFaces Migration Issues 3.1.x - 3.2.0
This chapter includes only those issues that concern migration from from 3.1.x versions to 3.2.0. Issues, related to the new components and other problems are not covered here. However, Jira [http://jira.jboss.com/jira/browse/RF] contains all issues and if you can not find your case there, please, feel free to report it.
4.1. Most important issues
Migrating to RichFaces 3.2.0 you can encounter with malfunction of the components caused by a number of reasons. However, most of the problems can be positively solved. This section covers the most significant issues you can potentially encounter, providing ways to handle the cases.
non-ASCII characters in application with i18n
An application with i18n does not work correctly due to the validation error that occurs when non- ASCII characters are used.
22.214.171.124. How to reproduce
... <select id="j_id27:cbxUser" name="j_id27:cbxUser" size="1" style="width:120px"> <option value="Al Korbeli& #269;o">Al Korbeli& #269;o</option> <option value="Al Nagyov& aacute;">Al Nagyov& aacute;</option> <option value="Al Tothov& aacute;">Al Tothov& aacute;</option> <option value="An Gajdov& aacute;">An Gajdov& aacute;</option> ... </select> ...
Bug is caused by the<rich:fileUpload> component