[
https://issues.apache.org/jira/browse/MYFACES-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865167#action_12865167
]
Werner Punz commented on MYFACES-2700:
--------------------------------------
Ok after talking to the EG I came to the conclusion that it might be ok to fix
the viewstates only on the processed elements (aka issuing and rendered ones)
A full update is a no go due to portlet concerns.
I already have coded it, but it needs further testing before committing the
code.
The code probably will be committed by monday!
> ajax usecase fails
> ------------------
>
> Key: MYFACES-2700
> URL: https://issues.apache.org/jira/browse/MYFACES-2700
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Werner Punz
>
> following usecase fails
> <h:form id="a">
> <h:commandButton action="#{TestBean.action}" value="submit"/>
> </h:form>
> <h:form>
> <input type="button" value="ajax ReRender"
> onclick="jsf.ajax.request(this,event,{execute:'@form',render:'a',
> onevent:function(data){alert(travelObjectString(data))}})"/>
> </h:form>
> this is a generic problem of both implementations I will investigate the
> problem and check if there is a way to get this up and running. The problem
> stems from the fact that javascript dialog frameworks manipulate the dom tree
> because position fixed does not work so they rely on dom shifting, which also
> means you have to embed a form into the dialog which when the dialog itself
> is ajaxed failes due to having the viewState not set properly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.