renderRegionOnly and DataScrollerPhaseListener incompatibili

[pbrewer_uk]

I have the following setup in my code:

E.g.

...
 <a4j:outputPanel ajaxRendered="true">
 <ui:fragment rendered="#{entityList.expensiveCall}">
 <rich:dataTable ...>
 ...
 </richdataTable>
 </ui:fragment>
 </a4j:outputPanel>
...
 <a4j:region renderRegionOnly="true">
 <a4j:jsFunction name="showDialog" reRender="dialogOutputPanel" action="#{dialogs.displayDialog}" limitToList="true" />
 <a4j:outputPanel id="dialogOutputPanel">
 <a4j:modalPanel showWhenRendered="true" rendered="#{dialogs.visible}">
 ...
 </a4j:modalPanel>
 <a4j:outputPanel>
 </a4j:region>
...

In 3.1.4.GA, this code behaved as expected, only traversing the component tree inside the region. But in 3.2.x,
when a call to showDialog is made, the org.richfaces.component.DataScrollerViewPhaseListener always traverses the entire component tree, making calls to isRendered() while looking for rich:datascroller components - this can cause an expensive (database) function to be called (e.g. {entityList.expensiveCall}).

Is there any way to disable this DataScrollerViewPhaseListener or a way to make it adhere to the renderRegionOnly logic? Or any other hints of suggestions to solve this would be greatly appreciated.

Thanks in advance,
Peter.

[pbrewer_uk]

Also, I forgot to mention that I'm not even using a rich:datascroller component on my page.

[hhuber]

I have the same problem.

DataScrollerViewPhaseListener tries to evaluate a rendered attribute that lies outside the region to be processed or rerendered. what's more, there's no datascroller on the page at all.

using 3.2.0.SR1

[pbrewer_uk]

Sorry, I should have updated the status of this thread. I have created a jira issue:

https://jira.jboss.org/jira/browse/RF-3488

but as a workaround, you can hack the richfaces-ui-3.2.0.SR1.jar by modifying the META-INF/faces-config.xml and remove/ comment out the following lines.

<lifecycle>
 <phase-listener>
 org.richfaces.component.DataScrollerPhaseListener
 </phase-listener>
</lifecycle>

Be warned though: this will prevent pagination-synchronisation on data scroller components. e.g. if the dataset shrinks to a single result while viewing say page 3, you will see an empty page 3 instead of resetting back to page 1.

Hope this helps,

Pete.