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

[Matej Novotny (JIRA)]

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

Matej Novotny commented on RF-13230:
------------------------------------

Ok I can see what you mean now.
I re-used the sample and added a4j:commandButton calling a bean method (setting state to null) and rendering the table.
But try as I might I cannot make this working on 4.3.3.Final where you claim this should work (obviously it does not work on 4.3.x either). I even tried using differently annotated beans (managed, session or view scoped) but with no effect.

Therefore so far, this seems to be a bug but not a regression. If you really got this working on 4.3.3 I wonder if you would have a working sample to show. Until then I am removing the regression label.
Also I will write a test for this issue so we are able to resolve this problem.
                
> 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