Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Mon, 14 Apr 2014 16:18:15 +0000 (UTC)
From: "Leonardo Uribe (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: <JIRA.12708302.1397492226122.110572.1397492295167@arcas>
In-Reply-To: <JIRA.12708302.1397492226122@arcas>
References: <JIRA.12708302.1397492226122@arcas>
Subject: [jira] [Created] (MYFACES-3883) c:forEach with PSS enabled fails
 when added rows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Leonardo Uribe created MYFACES-3883:
---------------------------------------

             Summary: c:forEach with PSS enabled fails when added rows
                 Key: MYFACES-3883
                 URL: https://issues.apache.org/jira/browse/MYFACES-3883
             Project: MyFaces Core
          Issue Type: Bug
            Reporter: Volker Weber
            Assignee: Leonardo Uribe


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)