myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3574) Update of 'javax.faces.ViewState' input elements fails
Date Tue, 25 Feb 2014 12:16:20 GMT


Werner Punz commented on MYFACES-3574:

Well there is a programmatic way, you could extract the jsf.js of a later myfaces version
and inject that one into your page instead of the official jsf.js (the first import must be
your jsf.js just in case other components try to import the official jsf.js which then is
Since both fixes are pure javascript I do not see any reason why this approach should not

> Update of 'javax.faces.ViewState' input elements fails
> ------------------------------------------------------
>                 Key: MYFACES-3574
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.1.7, 2.1.8
>         Environment: Internet Explorer 7
>            Reporter: Mircea Toma
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.15, 2.1.9
>         Attachments: MYFACES-3574.patch
> The issue resides in the JS code that is responsible for updating javax.faces.ViewState
key in the hidden input elements. 
> In IE7 during the second update the lookup for the 'javax.faces.ViewState' named input
element fails. The element[name] syntax is used for the lookup which is known to fail for
elements with complex names (such as 'javax.faces.ViewState'). 
> When the lookup fails to find the input element a second input element is created which
will contain the new javax.faces.ViewState value. The next submit will send two 'javax.faces.ViewState'
parameters but only the first one (the oldest) is read by the server state manager . This
old key is not known to the server anymore and  this causes a ViewExpired exception to be
thrown on the server.

This message was sent by Atlassian JIRA

View raw message