[ 
https://issues.apache.org/jira/browse/MYFACES-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886642#action_12886642
 ] 

Werner Punz edited comment on MYFACES-2799 at 7/9/10 4:36 AM:
--------------------------------------------------------------

After sleeping over things, I do not want to doctor in this area anymore. I 
filed a bugreport regarding the problems a while ago on the JSF2.1 side
and it should be resolved on protocol level by further extensions to our 
viewstate handling specification on the ppr protocol.
(including client ids for the viewstate forms)

I have to add, cross form submit are already properly resolved by resolving 
forms which are related to the render cycle, so we have a workaround (although 
incompatible to mojarra which has non working fixup code) to the problem. So 
any further work on this issue, without getting the spec changes needed to fix 
it once and forall is pointless.



      was (Author: werpu):
    After sleeping over things, I do not want to doctor in this area anymore. I 
filed a bugreport regarding the problems a while ago on the JSF2.1 side
and it should be resolved on protocol level by further extensions to our 
viewstate handling specification on the ppr protocol.
(including client ids for the viewstate forms)

  
> JSF 2.1: jsf.js viewstate handling does not entirely work out (bug filed on 
> the spec tracker
> --------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-2799
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2799
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.0.2-SNAPSHOT
>            Reporter: Werner Punz
>
> Only issuer form and render target forms currently are updated, execute forms 
> should be as well. 
> This entire update mess again is caused by portlets constraints
> theoretically all forms within the document should be updated with their 
> viewstates on server side state saving, we cannot do that due to 
> having also to be able to run in portlets
> , we need a reliable portlet detection to fix this issue properly.
> (Burgreport on the jsf side is filed)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to