[ https://issues.apache.org/jira/browse/TRINIDAD-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007645#comment-13007645 ]
Pavitra Subramaniam commented on TRINIDAD-2058: ----------------------------------------------- Hello Volker, You are right. This issue (encountered when adding debug-output) seemed vaguely familiar and I remembered that I ran into the same issue a year ago and at that time after discussing with Trinidad members we decided the solution needs to come from JSF RI. See related bug http://java.net/jira/browse/JAVASERVERFACES-1441. Your patch may have to be applied as an interim fix. Thanks Pavitra > PPR request doesn't update components > ------------------------------------- > > Key: TRINIDAD-2058 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2058 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components > Affects Versions: 2.0.0-beta-2 > Environment: WinXP, IE 8, Firefox 3.6, Tomcat 5.5 > Reporter: Volker Malzahn > Attachments: Page.js, page.js > > > A PPR request which contains one or more "update" elements doesn't updates > these components in the browser. > Reason: same as in issue TRINIDAD-1837, but with 2.0.0-beta-2 this doesn't > happen for some rare cases but for all PPR requests (in my environment) > because the new format of the PPR response always has an HTML comment as > first child node of an "update" element. > Solution is easy: just merge the changes of TRINIDAD-1837 to the 2.0.0 branch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira