[
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196201#comment-16196201
]
Werner Punz commented on MYFACES-4160:
--------------------------------------
While trying 4156 I found another issue in the rendered markup:
First at initial page load the page was basically perfectly rendered, once I
tried to hit the login button following response came
<partial-response id="j_id__v_0"> <!-- which puts the code into naming mode
response -->
<update id="helloForm"><![CDATA[<form id="helloForm" name="helloForm" ....
this part is fine]]></update>
<update id="j_id__v_0:javax.faces.ViewState:1">
<![CDATA[twZolpqJiEguoybbPiqYMTE+F29uqaLxrBUOm3Bj6vDo6C1m]]></update>
Now this is problematic
a) the response is prefixed wich puts the code into naming mode which means
only the elements with the prefix j_id__v_0 will be updated...
which then means the viewstate update will only update form2 not form1, because
of the prefix and hence you again run into viewstate sync issues:
there seems to be the first form being omitted from the viewroot id.
> ViewState not written for Ajax request
> --------------------------------------
>
> Key: MYFACES-4160
> URL: https://issues.apache.org/jira/browse/MYFACES-4160
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.3.0-beta
> Reporter: Thomas Andraschko
> Assignee: Werner Punz
> Fix For: 2.3.0
>
>
> If you run the application from MYFACES-4156 via mvn jetty:run, the
> viewStateId isn't rendered again after the first ajax request.
> Seems like FaceletViewDeclerationLanguage line 1910 should handle that but it
> skips.
> [~lu4242] Could you please check that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
