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

Werner Punz edited comment on MYFACES-4517 at 2/2/23 3:53 PM:
--------------------------------------------------------------

Could be a duplicate, fixed not very likely, I did a sync on the latest main 
codebase today, and still got the TCK fail in!

I will resync tomorrow and do another check!

 


was (Author: werpu):
Could be a duplicate, fixed not very likely, I did a sync on the latest master 
codebase today, and still got the TCK fail in!

I will resync tomorrow and do another check!

 

> TCK Testing Issue 5: Faces 2.2 - Issue3833IT State is lost in ui:repeat 
> submits
> -------------------------------------------------------------------------------
>
>                 Key: MYFACES-4517
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4517
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.3-next-M7, 4.0.0-RC2
>         Environment: Test Setup:
> Apache MyFaces 4.0, Typescript faces.js pull request branch:
> (https://github.com/apache/myfaces/pull/356)
> Tck Tests:
> https://github.com/werpu/tckworkbench
> (compile the 4.0 pr branch and then run the tests via maven in the workbench)
>            Reporter: Werner Punz
>            Priority: Major
>
> We trigger explicitely the error this case is testing for.
> At the third submit the initial viewstate is picked up instead of the update 
> one
> and hence losing the before value.
> The incoming viewstate from the Ajax cycle however is properly updated on the 
> client.
> So there is an indication that the problem is somewhere on the server.
>  
> See also [https://github.com/apache/myfaces/pull/356#issuecomment-1336971903] 
> for a more detailed description of the issue



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to