[richfaces-issues] [JBoss JIRA] (RF-13095) extendedDataTable tableState setter not called on column resize/reorder

[Brian Leathem (JIRA)]

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

Brian Leathem commented on RF-13095:
------------------------------------

I committed a test showing the tableState setter is called:
https://github.com/richfaces4/components/commit/69b918c183b736d594781f39caeb9b92f9778a76

[~salvois] can you please provide a code sample demonstrating that the setter is not called?  We are approaching code freeze for 4.3.4, so please consider providing this code sample in a timely manner.
                
> extendedDataTable tableState setter not called on column resize/reorder
> -----------------------------------------------------------------------
>
>                 Key: RF-13095
>                 URL: https://issues.jboss.org/browse/RF-13095
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.2
>         Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23, tested on Firefox 22 and Chrome 28.
>            Reporter: Salvo Isaja
>            Assignee: Brian Leathem
>             Fix For: 4.3.4
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Not sure if this qualifies as a bug or a feature request.
> I have an extendedDataTable with the tableState attribute bound to a String property of a backing bean (tried both a request scoped bean on a transient view and a session scoped bean on a stateful view).
> When resizing or reordering columns, an Ajax request is posted to the server, and I correctly see the new column layouts in the request, but the setter of the tableState property in the backing bean is not called. If I execute @form on a a4j:commandLink or commandButton, it is called instead.
> Thanks

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