ExtendedDataTable reRendered even if out a4j:region with renderRegionOnly=true ------------------------------------------------------------------------------ Key: RF-6482 URL: https://jira.jboss.org/jira/browse/RF-6482 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: Windows XP PRO SP2 Glassfish V2 UR2 JSF 1.2_09 JSP, Not using Facelets Affects: FF and IE Reporter: Nicolas Gaudin Hi all, I have several a4j:include all in one page : - TREE: one for a tree of folders (not system folders, but categories of items) - EDT: one for a list of items belonging to a particular category (the EDT) - ITEM: one containing the detail of each item (rerendered when clicking on a row of the EDT) so when clicking on a treeNode of TREE, the list of items is reRendered via a4j:support with reRender="dataTable" : this is working OK BUT, when I do operation on the tree (ex:DnD, deletion of a node via contextmenu, etc...each time an ajax request is sent (via a4j:support mainly), EDT is reRendered in BACKEND. I mean by "backend" that it is not visual on the UI but I see it occurs in my log. This impacts a lot the performance of my application. ALSO, when user changes the details of a selected item (ITEM include) and use a suggestionbox (for instance), again i see in the log that the EDT is Rerendered. ITEM include (not like the TREE that needs to actually rerender the EDT or the EDT that needs to actually rerender the ITEM) has nothing to do (no rerender interaction) with the TREE or the EDT. So, I tried to encapsulate ITEM include in a4j:region with attribute renderRegionOnly set to TRUE. Nothing seems to work.. This only thing i can say is that it has perhaps something to do with EDT tablestate???? because i see it in the log (having logged getTableState in managed bean) at the beginning AND at the end of this weird rerendering thing Do you have any idea on this, any quick workaround? Many thanks in advance for your answers Nicog -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira