myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <>
Subject [jira] Issue Comment Edited: (MYFACES-2700) ajax usecase fails
Date Wed, 05 May 2010 12:45:02 GMT


Werner Punz edited comment on MYFACES-2700 at 5/5/10 8:43 AM:

Ok again mojarra only fixes this if you render directly the form, this behavior also is error
prone. in reality an incoming javax.faces.ViewState should update all forms in the page nothing
more and nothing less.

      was (Author: werpu):
    Ok I tested it, as it seems mojarra does following, it just changes the viewstate if the
update elements contain a form which means they do following

udate -> identifier identifier...
javax.faces.ViewState -> issuing element, updated elements if they contain forms

> ajax usecase fails
> ------------------
>                 Key: MYFACES-2700
>                 URL:
>             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',
> </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.

View raw message