[
https://issues.apache.org/jira/browse/MYFACES-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856085#action_12856085
]
Leonardo Uribe edited comment on MYFACES-2654 at 4/12/10 2:03 PM:
------------------------------------------------------------------
Yes, we know that. This was my last post on dev list:
".....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......."
I think it is possible to move the code from RenderResponseExecutor to jsp
vld.buildView().
Max Starets says this:
"...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..."
So the problem is not the mapping. As I said before, the problem is trinidad
overrides completely PartialViewContextImpl.
In this case, allow an implementation to override PartialViewContextImpl takes
precedence over allow ajax work in jsp case, so as first solution the code
should be removed.
was (Author: lu4242):
Yes, we know that. This was my last post on dev list:
".....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......."
I think it is possible to move the code from RenderResponseExecutor to jsp
vld.buildView().
Max Starets says this:
> 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";
> 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:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
