[richfaces-issues] [JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off

[Andrey Zhemoytuk (JIRA)]

     [ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Zhemoytuk updated RF-13111:
----------------------------------

    Labels: partial_state_saving  (was: lazy-loaded)

    
> Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13111
>                 URL: https://issues.jboss.org/browse/RF-13111
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>         Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
>            Reporter: Andrey Zhemoytuk
>            Assignee: Brian Leathem
>              Labels: partial_state_saving
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
>      <rich:dataTable value="#{myBean.property}" rendered="false">
>       </rich:dataTable>
> </h:form>
> {code}
> Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
> I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.

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