myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (MYFACES-2700) ajax usecase fails
Date Wed, 05 May 2010 10:31:06 GMT

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

Werner Punz commented on MYFACES-2700:
--------------------------------------

Ok this is a spec deficit:
The spec says in the jsdocs:
# If an update element is found in the response with the identifier javax.faces.ViewState:

<update id="javax.faces.ViewState">
   <![CDATA[...]]>
</update>

locate and update the submitting form's javax.faces.ViewState value with the CDATA contents
from the response.

(jsdocs/symbols/jsf.ajax.html)

the problem now is that the view state element is not rendered upon ppr on a form and this
normally would not be a problem if the original form is the issuing, but if the issuing form
is another one than the view state is lost.
The question to me is whether this is expected behavior, after all the viewState element should
be present after a form ppr update just like it is after the first rendering, I assume.

I will dig deeper in this regard.
This problem is on both implementations btw.


> 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.


Mime
View raw message