[
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183102#comment-16183102
]
Thomas Andraschko edited comment on MYFACES-4160 at 9/27/17 7:19 PM:
---------------------------------------------------------------------
Checked that case again and i remember now that the forms were always rendered
without viewstate id and was applied via JS.
Now looking why it doesn't work - Somehow we also have 2 AjaxResponse.js.
Seems like AjaxResponse.js instead AjaxResponse22.js is used, we definitely
need a cleanup here.
was (Author: tandraschko):
Checked that case again and i remember now that the forms were always rendered
without viewstate id and was applied via JS.
Now looking why it doesn't work - Somehow we also have 2 AjaxResponse.js.
> 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
> 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)
