[
https://issues.apache.org/jira/browse/MYFACES-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861874#action_12861874
]
Jakob Korherr commented on MYFACES-2666:
----------------------------------------
This works now :)
I moved all the ResponseSwitch-related stuff from impl to shared to be able to
use it in JspViewDeclarationLanguageBase. The ResponseSwitching-algorithm is
now the following:
In JspVDLBase.buildView() a ResponseSwitch is installed and disabled, so that
nothing can be written while the view is built from JSP (via JSP forward) -
normally this is all the stuff that comes before <f:view>. Then in
JspVDLBase.renderView() the ResponseSwitch is re-enabled in order to let all
components render their output. After the rendering (and after the state is
written) the ResponseSwitch is disabled again to prevent anything that comes
after </f:view> from beeing written.
I really do hope this was the last time we had problems related to the
ResponseSwitch!
> 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
> Fix For: 2.0.1-SNAPSHOT
>
> 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.
