myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Resolved] (MYFACES-3883) c:forEach with PSS enabled fails when add multiple rows
Date Mon, 14 Apr 2014 16:28:15 GMT

     [ https://issues.apache.org/jira/browse/MYFACES-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Leonardo Uribe resolved MYFACES-3883.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.3
                   2.1.16
                   2.0.22

> c:forEach with PSS enabled fails when add multiple rows
> -------------------------------------------------------
>
>                 Key: MYFACES-3883
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3883
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314, JSR-344
>            Reporter: Volker Weber
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.22, 2.1.16, 2.2.3
>
>
> It has been reported that c:forEach tag with PSS enabled doesn't work well, but if PSS
is disabled it works again.
> This problem has been known for a long time, but it was considered a flaw in c:forEach
tag, and there are know fixes for it:
> 1. Set javax.faces.PARTIAL_STATE_SAVING to false.
> or
> 2. Add the page in javax.faces.FULL_STATE_SAVING_VIEW_IDS (disable PSS
> on the related page only).
> or
> 3. Set org.apache.myfaces.REFRESH_TRANSIENT_BUILD_ON_PSS_PRESERVE_STATE to true.
> In JSF 2.2 we fixed that tag from root, but it seems possible to add a small workaround
over the state saving algorithm to fix at least the duplicate id exception. It is not perfect,
but it seems enough in some cases, and the tag will look "less broken". The idea is detect
the duplicate when the component is added to the tree and remove the invalid component and
replace it with the restored one.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message