[richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render

[Immo Benjes (JIRA)]

    [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930717#comment-12930717 ] 

Immo Benjes commented on RF-13230:
----------------------------------

Sorry I confused the issues here. Two different bugs, the forum is indeed for RF-13226.

You wrote:
{code}
Changing the column ordering - JSON String is correctly passed to the bean and stored.
Setting its value to null using ajax - used a4j:commandButton, set to null, variable was null
Rerender component - nothing happened, table is still modified
{code}
The table should be back to default state when you reset the tableState and that is not happening. 
                
> Resetting table state on extendedDataTable does not reset table when using ajax re-render
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13230
>                 URL: https://issues.jboss.org/browse/RF-13230
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Matej Novotny
>              Labels: regression
>             Fix For: 4.3.5
>
>
> On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering  and column width. Only when reloading the complete page, the table is displayed in its default form.
> To reproduce:
> rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same.
> This used to work on RF 4.3.3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira