[
https://issues.jboss.org/browse/RF-12807?page=com.atlassian.jira.plugin.s...
]
Kenny Moens edited comment on RF-12807 at 3/5/13 1:54 AM:
----------------------------------------------------------
Brian Leathem: I've tried with setting the rendered condition on the dataTable itself.
It does not change the results and gives the same issue.
I tried this with the attached file (dataTableBug2.jsf).
Additionally if we make use of the c:if tag it works properly. While this is an acceptable
workaround, still the rendered property should not allow any of the child components to be
considered for execution at all (see dataTableBug3.jsf).
Note: it should be easily to reproduce based on the attached files.
was (Author: kmoens):
Brian Leathem: I've tried with setting the rendered condition on the dataTable
itself. It does not change the results and gives the same issue.
I tried this with the attached file (dataTableBug2.jsf).
Additionally if we make use of the c:if tag it works properly. While this is an acceptable
workaround, still the rendered property should not allow any of the child components to be
considered for execution at all.
Note: it should be easily to reproduce based on the attached files.
Datatable evaluate value attribute even if rendered=false when doing
ajax calls
-------------------------------------------------------------------------------
Key: RF-12807
URL:
https://issues.jboss.org/browse/RF-12807
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core, component-tables
Affects Versions: 4.3.0.Final
Environment: Windows, Apache Tomcat 6/7, Mojorra JSF 2.1.18
Reporter: Kenny Moens
Labels: ajax, commandButton, datatable, lazy-loaded, waiting_on_user
Attachments: Bean.java, dataTableBug.jsf, dataTableBug2.jsf, dataTableBug3.jsf
The rich:dataTable component evaluates the EL expression inside the value attribute, upon
an Ajax call, even if it is part of a non-rendered h:panelGroup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira