[richfaces-issues] [JBoss JIRA] Updated: (RF-4075) Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076

[Jay Balunas (JIRA)]

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

Jay Balunas updated RF-4075:
----------------------------

        Summary: Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076  (was: Regression!!! Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076)
    Component/s: regression


> Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076
> -----------------------------------------------------------------------------------------------------
>
>                 Key: RF-4075
>                 URL: https://jira.jboss.org/jira/browse/RF-4075
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-tables, regression
>    Affects Versions: 3.2.1
>            Reporter: Michael Youngstrom
>            Assignee: Alexander Smirnov
>            Priority: Minor
>             Fix For: 4.0.0.ALPHA2
>
>
> RF-2076 created a major Regression in RichFaces.  This has been a long standing spec bug that a4j iterables were able to avoid for a long time.
> https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=153
> The problem is that now all my code depends upon the behavior of not discarding saved values.  Would it be possible to add a "compatibility" flag to the iterable components that will allow them to behave the way they used to in not discarding saved state but allow those who want to match h:dataTable broken functionality can set it to true?
> This issue is also related to RF-2076 which was rejected.  This issue is different from RF-2076 because it is specifically requesting both functionalities.
> Mike

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