[
https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197309#comment-16197309
]
Werner Punz edited comment on MYFACES-4154 at 10/9/17 5:02 PM:
---------------------------------------------------------------
Adding the comment from 4162
I just checked the usecase, that is unrelated to the ajax code.
Following, the login page makes an ajax navigation. The response sends a
viewstate of:
<div id="javax_faces_developmentstage_messages"></div></body>
</html>]]></update><update
id="j_id__v_0:javax.faces.ViewState:1"><![CDATA[me7tJGl/CI84yKJsvkcXExVnpbdtkAQNHiQQUGUK4Hvx2E29]]></update></changes></partial-response>
which apparently ends up in the form as following element:
<input type="hidden" id="j_id__v_0:javax.faces.ViewState:0"
name="j_id__v_0:javax.faces.ViewState"
value="me7tJGl/CI84yKJsvkcXExVnpbdtkAQNHiQQUGUK4Hvx2E29">
As you can see a perfectly valid viewstate
Now the logout button is a normal non ajaxed button
<form jsfc="h:form">
<ui:insert name="header" >
<ui:include src="/lifeheader.xhtml" />
</ui:insert>
where the logout button is in ui:include:
<ui:composition>
<input jsfc="h:commandButton" style="background-color:#F78181; padding: 10px;"
type="submit" id="signOut" value="SignOut" action="signedOut" actionListener="#
{userBean.signOut}
"/>
now what happens if i press the first signout, I end up back on the same page
apparently something in the myfaces 2.3 navigational code is messed up here,
but not on the ajax side. Either the server sends a wrong viewstate back at the
ajax request or something else is broken in this usecase.
By pressing the button a second time I finally have the correct viewstate and
the navigation goes forward back to the login page.
Sorry there is nothing I can do on my side here, the viewstates coming in from
the server are correctly inserted. The server guys need to debug that out.
Just a sidenote, I replaced quickly our implementation in the pom.xml with the
mojarra binaries. Mojarra 2.3.2 navigates correctly.
was (Author: werpu):
Adding the comment from 4162
I just checked the usecase, that is unrelated to the ajax code.
Following, the login page makes an ajax navigation. The response sends a
viewstate of:
<div id="javax_faces_developmentstage_messages"></div></body>
</html>]]></update><update
id="j_id__v_0:javax.faces.ViewState:1"><![CDATA[me7tJGl/CI84yKJsvkcXExVnpbdtkAQNHiQQUGUK4Hvx2E29]]></update></changes></partial-response>
which apparently ends up in the form as following element:
<input type="hidden" id="j_id__v_0:javax.faces.ViewState:0"
name="j_id__v_0:javax.faces.ViewState"
value="me7tJGl/CI84yKJsvkcXExVnpbdtkAQNHiQQUGUK4Hvx2E29">
As you can see a perfectly valid viewstate
Now the logout button is a normal non ajaxed button
<form jsfc="h:form">
<ui:insert name="header" >
<ui:include src="/lifeheader.xhtml" />
</ui:insert>
where the logout button is in ui:include:
<ui:composition>
<input jsfc="h:commandButton" style="background-color:#F78181; padding: 10px;"
type="submit" id="signOut" value="SignOut" action="signedOut" actionListener="#
{userBean.signOut}
"/>
now what happens if i press the first signout, I end up back on the same page
apparently something in the myfaces 2.3 navigational code is messed up here,
but not on the ajax side. Either the server sends a wrong viewstate back at the
ajax request or something else is broken in this usecase.
By pressing the button a second time I finally have the correct viewstate and
the navigation goes forward back to the login page.
Sorry there is nothing I can do on my side here, the viewstates coming in from
the server are correctly inserted. The server guys need to debug that out.
Just a sidenote, I replaced quickly our implementation in the pom.xml with the
mojarra binaries. Mojarra 2.3.2 navigates correctly.
> The browser (chrome) always show the previous page name while its on the
> current page rendered properly
> -------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-4154
> URL: https://issues.apache.org/jira/browse/MYFACES-4154
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.3.0-beta
> Reporter: Dora Rajappan
> Priority: Minor
> Attachments: mf23test.zip
>
>
> The browser (chrome) always show the previous page name while its on the
> current page rendered properly . This bug is already logged in jira not sure
> of the bug id. Not sure its browser problem or jsf. Not checked this with
> mojarra also.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
