Is the default renderRegionOnly set to true or false.?
There is inconsistent info in documentation:
- in description it says default is false
- in key attributes and ways of usage :
The processing could be also accelerated if a region decoded for the processing passes straight
away into Encode. But to update some data out of the region or on another region, use the
"renderRegionOnly" attribute set to "false" ("true" on default) to change this behaviour.
So what is the correct one?
More, I have really weird behaviour (RF 3.3.0GA) with a4j:region.
My page architecture is as follows:
- the main page 'MAIN' polling for session check
- a a4j:include in 'MAIN' called 'EXPLORER'
- two a4j:include in 'EXPLORER' called 'TREE' (form with rich:tree) and 'LIST' (form with rich:extendedDataTable)
Weird behaviour of a4j:region:
TREE include contains a rich:tree in h:form. the tree uses several a4j:support for onclick, DnD, deletion of treeNode via contextmenu,etc..
When clicking on a treeNode, the 'LIST' include gets actually and visually rerendered by reRender attributes of a4j:support for onclick event.
This is working fine without any region, EXCEPT that the 'LIST' include gets also rerendered (not visually but in the log) for all ajax request sent by others a4j:support (event ondrag for instance)
==> SO, Just for checking because I do not want to do that as I need to actually rerender the LIST include after node click but anyway:
I added an a4j:region (renderRegionOnly=TRUE) around the rich:Tree, BUT same result: the extended data table gets rerendered at each ajax Request sent by an a4j:support ???
2nd case: Polling to check session in main page
i have a a4j:poll encapsulated in h:form and a4j:region (in this order: <h:form><a4j:region><a4j:poll>...) with renderRegionOnly forced to true at he beginning of 'MAIN' page.
==> When poll is triggered, I get the rich:tree in TREE include of EXPLORER that gets rerendered (not visually, but in the log)... but not the extendedDataTable contained in LIST include of EXPLORER include...
I also tried removing all a4j:includes and putting all in same page...same results..
I originally thought the problem of this weird behaviour of a4:region was coming from extendedData table and particularly tableState management)...
but with this 2nd case.....I am getting completly lost here..
Could anyone explain to me why all this happens?
This is critical for the performance of my application that I can limit the regions
Sincerely hope somebody ca help me on this as I am becoming crazy..
Best regards to all,