X hits on this document

52 views

0 shares

0 downloads

0 comments

18 / 20

Chapter 5. The RichFaces Migration Issues 3.2.x

  • -

    3.3.0

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

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 [http://jira.jboss.org/jira/browse/RF-3341]

  • RichFaces

Forum

[http://www.jboss.com/index.html?

module=bb&op=viewtopic&p=4197996#4197996]

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" />

19

Document info
Document views52
Page views52
Page last viewedSat Dec 03 11:02:57 UTC 2016
Pages20
Paragraphs460
Words3352

Comments