JBoss.orgCommunity Documentation

RichFaces Migration Guide


1. Introduction
2. Scope of the document
3. Minimum requirements for the project with RichFaces 3.2.0
4. The RichFaces Migration Issues
4.1. Most important issues
4.1.1. non-ASCII characters in application with i18n
4.1.2. Menu components and JSF-RI-1.2_08
4.1.3. Binding problem in JSP
4.1.4. Ajax requests in JSF 1.2
4.1.5. Resources for standard skinning classes
4.2. Issues with upgrading from previous versions
4.2.1. <rich:calendar> and "ondateselected" event problem
4.2.2. Paired <rich:datascroller> components do not work
4.2.3. Static "for" attribute in <rich:datascroller>
4.2.4. The ajaxSingle/region components in facets of <h:dataTable>
4.2.5. Action listeners calling problem with <a4j:actionparam> on JSP page
4.3. Issues with compatibility with third party frameworks
4.3.1. The "fileUploadListener" with MyFaces or JSF-RI 1.2_04
4.3.2. RichFaces 3.2.0 with MyFaces 1.2.2 on WebLogic 10 MP1
4.3.3. <rich:fileUpload> with Seam multi-part filter

This document is aimed to provide guidelines for migrating RichFaces projects from 3.1.x versions to 3.2.0.

RichFaces Migration Guide covers troublesome issues caused by migration and provides suitable workarounds and examples.

You can find all technical requirements to start working with RichFaces 3.2.0 in the Developer Guide.

This chapter includes only those issues that concern migration from the previous versions to 3.2.0. Issues, related to the new components and other problems are not covered here. However, Jira contains all issues and if you can not find your case there, please, feel free to report it.

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.

This section covers issues you can encounter upgrading to RichFaces 3.2.0 from previous versions.

This section covers issues related to compatibility with third party frameworks.