myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] Commented: (MYFACES-2654) Trinidad ajax-branch does not work with MyFaces2
Date Mon, 12 Apr 2010 19:17:49 GMT


Leonardo Uribe commented on MYFACES-2654:

Unfortunately, we can't add implementation details to java api. Note this flag is myfaces
specific, and to remain compatible with ri, we cannot commit that kind of code. 

For example, in MYFACES-2616 the patch proposed uses a param to indicate when we are "marking
initial state". I can't commit that code because we need to include this facescontext attribute
on the spec to allow that code on api.

Could you test the suggestion about move the code from RenderResponseExecutor to JSP vld.buildView()?

> Trinidad ajax-branch does not work with MyFaces2
> ------------------------------------------------
>                 Key: MYFACES-2654
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.0.0-beta-3
>         Environment: Trinidad ajax branch, URL:
> MyFaces TRUNK
>            Reporter: Matthias We├čendorf
>         Attachments: MYFACES-2654.patch
> run the demo (like via Jetty):
> Go to "http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx"
> on any "ajax" action/click, I get these two alert() boxes:
> * "TypeError: this._ajaxOldDomElements is null"
> * "malformedXML--"
> Same stuff works with Mojarra 2.0.2

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message