Send your remarks, comments or wishes to doc team
Subject:
Message:
Your name:
Your email:

JBoss.org Community Documentation

- Prev

## Chapter 5. The RichFaces Migration Issues 3.2.x - 3.3.0

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.

## 5.1. Ajax request calls encode() methods of <rich:dataTable> even if it is not necessary

### 5.1.1. Description

Any Ajax request reloads the list that is related to the <rich:dataTable> component even if the Ajax request is related to another bean. It happens because the Ajax request checks whether the <rich:dataTable> has nested <rich:outputPanel> or <rich:messages> components that should be updated. If there are no <rich:outputPanel>, <rich:messages> components inside the <rich:dataTable> will not be updated, but anyway the `encode()` methods is called by the Ajax request.

### 5.1.2. Links

- Jira

- RichFaces Forum

### 5.1.3. How to reproduce

Place the following code on a page and click the button. The list in `myBean1.myList` will be reloaded.

    ...

    <h:form  id="form1">

        <rich:dataTable id="myTable" value="#{myBean1.myList}" var="comp">

            ...

        </rich:dataTable>

    </h:form>

    <h:form id="form2">

        <h:outputText value="#{myBean2.test}"/>

        <a4j:commandButton event="onclick" reRender="form2" />

    </h:form>

    ...

### 5.1.4. Causes

Bug is caused by <rich:dataTable> implementation peculiarity.

### 5.1.5. Workarounds

Wrap the zone of a page that should be processed and updated in the <a4j:region> component with `renderRegionOnly="true"`. The <rich:dataTable> should be outside of the <a4j:region>.

- PrevChapter 4. The RichFaces Migration Issues 3.1.x -...
- Top of page
- Front page