[
https://issues.apache.org/jira/browse/MYFACES-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735918#comment-17735918
]
Volodymyr Siedlecki commented on MYFACES-4605:
----------------------------------------------
Looks like the new viewstate id is caused by
_fetchUniqueId: function(prefix, identifier) {
var cnt = 0;
var retVal = prefix + identifier + jsf.separatorchar + cnt;
while(this._Dom.byId(retVal) != null) {
cnt++;
retVal = prefix + identifier + jsf.separatorchar + cnt;
}
return retVal;
},
The count starts at 0, and the evaluation sees that 0 is available, so it uses
it.
The Java code starts the id with 1 :
{color:#dcdcaa}HtmlResponseStateManager{color}
if (count == null)
{
count = Integer.valueOf(0);
}
count += 1;
> Cross form rending via ajax, form is missing ViewState
> ------------------------------------------------------
>
> Key: MYFACES-4605
> URL: https://issues.apache.org/jira/browse/MYFACES-4605
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 3.0.1, 2.3.10
> Reporter: Joe Crichton
> Assignee: Werner Punz
> Priority: Major
> Fix For: 2.3.11, 3.0.3
>
> Attachments: image-2023-06-20-21-22-50-593.png
>
>
> Seems this is an old issue, which was presumably fixed for MyFaces in 2.2 as
> discussed here
> [https://balusc.omnifaces.org/2011/09/communication-in-jsf-20.html#AjaxRenderingOfContentWhichContainsAnotherForm|https://balusc.omnifaces.org/2011/09/communication-in-jsf-20.html#AjaxRenderingOfContentWhichContainsAnotherForm),]
> and [https://github.com/jakartaee/faces/issues/790]
> Using openliberty with jsf-3.0 feature still has this occurring. Using the
> workaround outlined by the first link fixes the issue. I believe the same is
> true for the jsf-2.3 feature as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
