[TOMAHAWK-1545] Components inside detailStamp facet requires clientId reset each time setRowIndex is called

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.9
• Fix Version/s: 1.1.10
• Component/s: Extended Datatable
• Assignee: Leonardo Uribe
• Reporter: Leonardo Uribe
• Created: 02/Sep/10 15:29
• Updated: 27/Sep/10 21:37
• Resolved: 02/Sep/10 15:33

Description

Checking detailStamp behavior, it was found that sometimes setRowIndex does not reset clientId field using UIComponent.setId(getId()), which could cause problems with invokeOnComponent/visitTree algorithm.

It was also found that we have some code on processDetails(FacesContext, int) that saves the state of the row, that it is no longer necessary by the fix done on TOMAHAWK-1534. I think it is better instead save detailStamp state in AbstractHtmlDataTable, change the iterator overriding saveDescendantComponentStates() and restoreDescendantComponentStates(Object state), and on jsf 1.1 and 1.2 branches remove the hack for prevent processing detailStamp removing and adding from facets map.

We can also remove the hack for deleteRowStateForRow() on AbstractHtmlDataTable, because since the state will be in just one place, this problem is already handled on HtmlDataTableHack