myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <>
Subject [jira] Commented: (MYFACES-2654) Trinidad ajax-branch does not work with MyFaces2
Date Wed, 14 Apr 2010 15:23:50 GMT


Werner Punz commented on MYFACES-2654:

Ok I postponed my car pickup appointment to investigate this, bevor making a break for today
I want to post the info I could find:

Ok I need further information on this, since the problem on Matthiass side is in firefox,
which I cannot reproduce here.
First which demos fail I have checked out the latest snapshot trunk and on the page mentioned
above about 95% of all demos work for me, the failing 5% are not directly related but have
to be investigated separately.

Can you give me an exact workflow of a failing test, with the exact browser version to find
the bug. I cannot reproduce that nothing works here (fortunately)

Also, do all demos work on mojarra or do you have failing demos as well in the ppr case?

Here is a small screencast of what I am getting here (please bear in mind that it takes a
little bit for Youtube to process the video (so the video quality will take a while to get

> Trinidad ajax-branch does not work with MyFaces2
> ------------------------------------------------
>                 Key: MYFACES-2654
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-3
>         Environment: Trinidad ajax branch, URL:
> MyFaces TRUNK
>            Reporter: Matthias We├čendorf
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.0
>         Attachments: MYFACES-2654-2.patch, MYFACES-2654-3.patch, 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