Create new RichFaces Documentation Jira issue

This will launch the RichFaces Jira page - to complete your feedback please login if needed, and submit the Jira.

JBoss.orgCommunity Documentation

RichFaces Migration Guide

Last published: March 25, 2010

expand all
1. Introduction
2. Scope of the document
3. Minimum requirements for the project with RichFaces 3.2.0
+4. The RichFaces Migration Issues 3.1.x - 3.2.0
+4.1. Most important issues
+4.1.1. non-ASCII characters in application with i18n
4.1.1.1. Description
4.1.1.2. Links
4.1.1.3. How to reproduce
4.1.1.4. Causes
4.1.1.5. Workarounds
+4.1.2. Menu components and JSF-RI-1.2_08
4.1.2.1. Description
4.1.2.2. Links
4.1.2.3. How to reproduce
4.1.2.4. Causes
4.1.2.5. Workarounds
+4.1.3. Binding problem in JSP
4.1.3.1. Description
4.1.3.2. Links
4.1.3.3. How to reproduce
4.1.3.4. Causes
4.1.3.5. Workarounds
+4.1.4. Ajax requests in JSF 1.2
4.1.4.1. Description
4.1.4.2. How to reproduce
4.1.4.3. Causes
4.1.4.4. Workarounds
+4.1.5. Resources for standard skinning classes
4.1.5.1. Description
4.1.5.2. Links
4.1.5.3. How to reproduce
4.1.5.4. Causes
4.1.5.5. Workarounds
+4.2. Issues with upgrading from previous versions
+4.2.1. <rich:calendar> and "ondateselected" event problem
4.2.1.1. Description
4.2.1.2. Links
4.2.1.3. How to reproduce
4.2.1.4. Causes
4.2.1.5. Workarounds
+4.2.2. Paired <rich:datascroller> components do not work
4.2.2.1. Description
4.2.2.2. Links
4.2.2.3. How to reproduce
4.2.2.4. Causes
4.2.2.5. Workarounds
+4.2.3. Static "for" attribute in <rich:datascroller>
4.2.3.1. Description
4.2.3.2. Links
4.2.3.3. How to reproduce
4.2.3.4. Causes
4.2.3.5. Workarounds
+4.2.4. The ajaxSingle/region components in facets of <h:dataTable>
4.2.4.1. Description
4.2.4.2. Links
4.2.4.3. How to reproduce
4.2.4.4. Causes
4.2.4.5. Workarounds
+4.2.5. Action listeners calling problem with <a4j:actionparam> on JSP page
4.2.5.1. Description
4.2.5.2. Links
4.2.5.3. How to reproduce
4.2.5.4. Causes
4.2.5.5. Workarounds
+4.2.6. Behavior of the "immediate" attribute is changed
4.2.6.1. Description
4.2.6.2. Links
4.2.6.3. How to reproduce
4.2.6.4. Causes
4.2.6.5. Workarounds
+4.3. Issues with compatibility with third party frameworks
+4.3.1. The "fileUploadListener" with MyFaces or JSF-RI 1.2_04
4.3.1.1. Description
4.3.1.2. Links
4.3.1.3. How to reproduce
4.3.1.4. Causes
4.3.1.5. Workarounds
+4.3.2. RichFaces 3.2.0 with MyFaces 1.2.2 on WebLogic 10 MP1
4.3.2.1. Description
4.3.2.2. Links
4.3.2.3. How to reproduce
4.3.2.4. Causes
4.3.2.5. Workarounds
+4.3.3. <rich:fileUpload> with Seam multi-part filter
4.3.3.1. Description
4.3.3.2. Links
4.3.3.3. How to reproduce
4.3.3.4. Causes
4.3.3.5. Workarounds
+5. The RichFaces Migration Issues 3.2.x - 3.3.0
+5.1. Ajax request calls encode() methods of <rich:dataTable> even if it is not necessary
5.1.1. Description
5.1.2. Links
5.1.3. How to reproduce
5.1.4. Causes
5.1.5. Workarounds
+6. The RichFaces Migration Issues 3.3.0 - 3.3.1
+6.1. The <rich:contextMenu> if rendered completely disables right mouse click on a page
6.1.1. Description
6.1.2. Links
6.1.3. How to reproduce
6.1.4. Causes
6.1.5. Workarounds

This document is aimed to provide guidelines for migrating RichFaces projects.

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 in the Developer Guide.

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 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.

This chapter includes only those issues that concern migration from from 3.2.x versions to 3.3.0. Issues, that are 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.

This chapter includes only those issues that concern migration from from 3.3.0 versions to 3.3.1. Issues, that are 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.