Hi The problem is trinidad override PartialViewContext implementation, and on Render Response phase, the output is disabled. Myfaces PartialViewContextImpl enables it before render the output but trinidad doesn't know how to do that. Jira is down right now, so I'll put this comment as soon as is up again.
Maybe this is a good time to get rid response switch code. I did a fast check to mojarra and as I expected they are not doing anything. The point is ajax in jsp case will not work, and this code only has sense on jsp case (because vdl.buildView trigger dispatch and in jsp that render unwanted code). Note there is no "standard" way to know if the current page is for jsp or not, so we don't have a way to enable this code only for jsp case. regards, Leonardo Uribe 2010/4/9 Max Starets <[email protected]> > Werner, > > Thanks for the analysis. I don't think Myfaces is doing anything wrong in > this case - > our web.xml had javax.faces.FACELETS_VIEW_MAPPINGS mapped to *.jspx asd > well as *.xhtml > > I committed the change to leave *.xhtml only. > > I was unable to update the JIRA since Apache JIRA the site is down at the > moment. > > Max > > > Werner Punz (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/MYFACES-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855433#action_12855433 > ] > > Werner Punz commented on MYFACES-2654: > -------------------------------------- > > Ok I am not sure since I have not touched this area but the > ViewDeclarationFactoryImpl returns a Facelets View declaration on the files > passed by the demos, but those files are clearly jspx files. > The reason for this is that our default factory checks for facelets first and > has as allowed pattern jspx. > The files however are clearly not facelets! > Hence the wrong View Declaration Language is returned, this could be the > reason why the rendering is never triggered on the partial rendering (I still > wonder why it renders at all in the normal case) > In either way the problem is somewhere in the partial processing part of > myfaces! > I will forward this problem to Leonardo. > > > > > Trinidad ajax-branch does not work with MyFaces2 > ------------------------------------------------ > > Key: MYFACES-2654 > URL: https://issues.apache.org/jira/browse/MYFACES-2654 > Project: MyFaces Core > Issue Type: Bug > Affects Versions: 2.0.0-beta-3 > Environment: Trinidad ajax branch, URL: > https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3/ > MyFaces TRUNK > Reporter: Matthias Weßendorf > > run the demo (like via Jetty): > Go to "http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx"; > <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 > > > >
