[ https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198611#comment-16198611 ]
Werner Punz edited comment on MYFACES-4162 at 10/10/17 12:52 PM: ----------------------------------------------------------------- As I mentioned before... for non ajaxed cases use a redirect flag in your navigational definitions. This should fix it. https://www.mkyong.com/jsf2/jsf-page-forward-vs-page-redirect/ In the ajax navigational case, there is nothing we can do atm we probably would need a spec extension regarding url rewriting here, which at the time the ajax api was specified originally was not supported by any browser. was (Author: werpu): As I mentioned before... for non ajaxed cases use a redirect true flag in your navigational definitions. This should fix it. https://www.mkyong.com/jsf2/jsf-page-forward-vs-page-redirect/ In the ajax navigational case, there is nothing we can do atm we probably would need a spec extension regarding url rewriting here, which at the time the ajax api was specified originally was not supported by any browser. > bug in the response handling if a full page is sent via ajax > ------------------------------------------------------------ > > Key: MYFACES-4162 > URL: https://issues.apache.org/jira/browse/MYFACES-4162 > Project: MyFaces Core > Issue Type: Bug > Affects Versions: 2.3.0-beta > Reporter: Werner Punz > Assignee: Werner Punz > > The example in https://issues.apache.org/jira/browse/MYFACES-4154 sends back > an entire page due to a page navigation triggered from an ajax call, and > apparently the page is inserted but the viewstate is lost along the way. I > need to investigate what happens for such a corner case, since triggering a > page change navigation from Ajax is rather seldom but needs to be addressed. > I will need a handful of days to fix this, due to my limited time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)