[jira] [Resolved] (MYFACES-4204) Porlets: compatibility issues with view state handling on the client

["Werner Punz (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/MYFACES-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Werner Punz resolved MYFACES-4204.
----------------------------------
    Resolution: Fixed

Should work now, I reenabled the old way of doing things within the bounds of the jsf 2.3 spec (ala taking the new viewroot handling into consideration).

Which means we now follow the spec word by word. The old no_portlet_env hack also now works again which is a bypass to avoid endless update targets in multi form scenarii.

Please test it and reopen it if it does not work as expected.

 

> Porlets: compatibility issues with view state handling on the client
> --------------------------------------------------------------------
>
>                 Key: MYFACES-4204
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4204
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: Portlet_Support
>    Affects Versions: 2.3.0
>            Reporter: Niels Borman
>            Assignee: Werner Punz
>            Priority: Critical
>         Attachments: 1 - pageload.png, 10 - refreshbutton hit - network.png, 11 - refreshbutton hit - console.png, 12 - refreshbutton hit - source.png, 2 - pageload.png, 3 - refreshbutton hit.png, 4 - dialogbutton hit.png, 5 - dialogbutton hit - inspect.png, 6 - dialog refreshbutton hit.png, 7 - dialog refreshbutton hit - inspect.png, 8 - dialog closebutton hit.png, 9 - refreshbutton hit - network.png
>
>
> The problem arises from jsf.js because after an ajax call all javax.faces.ViewState hidden inputs are updated. The solution would be to update only those hidden inputs (javax.faces.ViewState) which are also within a form with the same action as the form in which the ajax call was executed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)