[
https://issues.apache.org/jira/browse/MYFACES-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911502#comment-13911502
]
John Redwood commented on MYFACES-3574:
---------------------------------------
I tested on chrome and on IE9/10 and same issues happening, Just not sure if
the problem was only for IE7 (reported issue) - If it effects others then yes
definitely look to upgrade our version but it is a long and tedious process to
get that done. If there is a programmatic way to do it quicker would be great..
At the moment It's looking like jQuery to update the forms input field even
though a second field has been added to the requests.
Doesn't seem to be the truncation issue though. Thanks heaps
> Update of 'javax.faces.ViewState' input elements fails
> ------------------------------------------------------
>
> Key: MYFACES-3574
> URL: https://issues.apache.org/jira/browse/MYFACES-3574
> 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
(v6.1.5#6160)
