[
https://issues.apache.org/jira/browse/MYFACES-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861439#action_12861439
]
Jakob Korherr commented on MYFACES-2666:
----------------------------------------
I just found the reason for this issue - (again) the ResponseSwitch. After a
lot of (Trinidad-)JavaScript debugging, I found out that the process is
completely the same on Mojarra and MyFaces. However on MyFaces the result of
the AJAX request is empty (Content-Length: 0) and thus Trinidad performs a full
page refresh. So Trinidad does the right thing here.
I think the problem exists, because there is a bug in Leonardo's solution for
MYFACES-2654. It seems like the ResponseSwitch is never enabled again, because
if you remove the code that disables the ResponseSwitch in
JspViewDeclarationLanguage.buildView(), the problem is gone (there is no full
page refresh anymore).
> Getting a full-page-refresh when running JSF's Ajax on the Trinidad 2 (trunk)
> -----------------------------------------------------------------------------
>
> Key: MYFACES-2666
> URL: https://issues.apache.org/jira/browse/MYFACES-2666
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0
> Reporter: Matthias Weßendorf
> Assignee: Jakob Korherr
> Attachments: pprDemos.jspx
>
>
> Running "pprDemos.jspx" page and triggering any ajax action, we see a
> full-page-refresh
> (tested with TRUNK of MyFaces2)
> Check out Trinidad trunk and change the pom.xml to take myfaces =>
> 2.0.1-SNAPSHOT instead of the beta-3
> go to trinidad-examples/trinidad-demo and trigger "mvn clean jetty:run
> -PjettyConfig"
> Now point a browser to this URL:
> http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
