[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=12928905#comment-12928905 ] 

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

I tried to reproduce this issue but I am not sure what behaviour should be expected. I tried it with ViewScoped bean first (later on I tried with Conversation too). 
Now following the steps in description (for 4.3.3)...
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
Full page refresh - nothing happened , table is still modified
Access page url again - table is loaded in default setup

This seems like the current table modifications are stored in a session or so as long as I don't switch from one page to another. Is the tableState meant to work as this issue describes it or is it a way to get hold of the table format to store it for future use (eg. when user comes back to website, the table will load based on last stored state)?

Back to Conversation bean, I tried to reproduce it with this one too and got the same result. However I cannot be sure I implemented it correctly since I never did it before. So [~ibenjes] could you provide a simple example where this feature was working for you with older RF? Without that I don't think I can reproduce this.
                
> 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