myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <>
Subject [jira] [Commented] (MYFACES-4160) ViewState not written for Ajax request
Date Sun, 08 Oct 2017 16:37:00 GMT


Werner Punz commented on MYFACES-4160:

Ah yes the second problem, intiially both viewstate elements were prefixed perfectly fine,
but upon replacement
the cdata block does not have a viewstate in, which also is fine, 
but then the <update id="j_id__v_0:javax.faces.ViewState:1">
<![CDATA[twZolpqJiEguoybbPiqYMTE+F29uqaLxrBUOm3Bj6vDo6C1m]]></update> comes along
and the viewstate element cannot be added to the first form anymore since the form id is not
prefixed with j_id__v_0

So I guess there are some bugs regarding the viewroot name handling.

Either leave out the j_id__v_0 for the partial response block so that all forms are picked
or put the prefix into all elements under this viewroot.

> ViewState not written for Ajax request
> --------------------------------------
>                 Key: MYFACES-4160
>                 URL:
>             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

View raw message