[
https://issues.apache.org/jira/browse/MYFACES-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864302#action_12864302
]
Werner Punz edited comment on MYFACES-2700 at 5/5/10 8:56 AM:
--------------------------------------------------------------
Ok this is an issue in both implementations, we loose the viewState element
entirely mojarra loses it if the render is not the form, but a parent element!
was (Author: werpu):
ok this seems to be a bug in our implementation, a testing against mojarra
revealed that the viewstate element
in this case is not lost, I assume mojarra is not as strict regarding the spec
as we are I am not sure yet if mojarra
just keeps the old view state element in the update form or simply drags the
emitted view state into all forms which are affected by the ppr request.
In either way it seems like the bug is on our side.
> 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.
