[richfaces-issues] [JBoss JIRA] Updated: (RF-5976) Multiple extendedDataTable on one page lead to a "Array index out of range"-Exception when user resizes a column of one of them

[Nick Belaevski (JIRA)]

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

Nick Belaevski updated RF-5976:
-------------------------------

    Fix Version/s: Future
         Assignee: Piotr Kawiak


> Multiple extendedDataTable on one page lead to a "Array index out of range"-Exception when user resizes a column of one of them
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-5976
>                 URL: https://jira.jboss.org/jira/browse/RF-5976
>             Project: RichFaces
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Marcel Urbanek
>            Assignee: Piotr Kawiak
>            Priority: Minor
>             Fix For: Future
>
>
> When I use only one extendedDataTable on a page, everything is fine. 
> When I use two or more extendedDataTable, with different number of columns, I get the following exception when I try to resize a column of the second table (if the tables have a different number of columns):
> Error 500: Array index out of range: 8 
> at org.richfaces.component.ColumnsSizeState.changeColumnSize(ExtendedDataTableState.java:337)
> Reason for that is the following: Richfaces seems to apply the changed column sizes to all(?) extendedDataTable in the View. It gets a little clearer whe you look at the requests that are submitted to the server:
> AJAXREQUEST	_viewRoot
> columnResizeAction	columnResizeAction
> columnWidths	67;69;154;231;67;231;144;17;
> This problem can be worked around, when I add a a4j:region around the tables. The Ajaxrequest then looks like the following:
> AJAXREQUEST	j_id10:workingTableRegion
> columnResizeAction	columnResizeAction
> columnWidths	67;67;156;231;67;314;61;17;
> So only the affected table is updated, no Exception occurs then.

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