[ 
https://issues.apache.org/jira/browse/MYFACES-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485018#comment-14485018
 ] 

Gonçalo Manuel Cruchinho commented on MYFACES-3964:
---------------------------------------------------

Leonardo,

I tested the fix available in the project's SVN and that fix breaks forEach 
tags that use a varStatus attribute, causing the second request on a view to 
fail.

When restoring an existing view that has a foreach tag with the varStatus 
attribute, the var attribute object is no longer the object expected and is 
switched with instances of IterationStatus.

To test just add a varStatus attribute to the forEach tag in the test case.

> c:foreach not working when using custom equals or non serializable objects
> --------------------------------------------------------------------------
>
>                 Key: MYFACES-3964
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3964
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.2.7
>            Reporter: Gonçalo Manuel Cruchinho
>            Assignee: Leonardo Uribe
>             Fix For: 2.2.8
>
>         Attachments: MyFaces22Test.war
>
>
> c:foreach doesn't work as intended when using an object with an overriden 
> equals. The same problem is observed when using an non serializable object. 
> In both cases the problem seems to be that the foreach component caches and 
> uses an outdated reference to the object.
> When using a serializable object with a non overwriten equals method, all 
> works as intended.
> When forcing org.apache.myfaces.STRICT_JSF_2_FACELETS_COMPATIBILITY as true 
> on the web.xml file, all works as intended.
> When using ui:repeat, all works as intended.
> I created a test case that demonstrates the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to