[
https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812763#comment-13812763
]
Dora Rajappan commented on MYFACES-3816:
----------------------------------------
And this behaviour true for redirect via navigation handler. In render phase it
goes to response complete and state saving is avoided.
<h:commandButton action="#{bean.action}" value="Invoke and redirect">
<f:ajax execute="@this"/>
</h:commandButton>
<navigation-rules>
<navigation-rule>
<from-view-id>/form.xhtml</from-view-id>
<navigation-case>
<from-action>#{bean.action}</from-action>
<from-outcome>success</from-outcome>
<to-view-id>/target.xhtml</to-view-id>
<redirect/>
</navigation-case>
</navigation-rule>
</navigation-rules>
@RequestScoped @ManagedBean
public class Bean {
public String action() { return "success"; }
}
I think its a good idea to follow client side state saving behaviour for ajax
redirect.
> missing window-handling for initial requests
> --------------------------------------------
>
> Key: MYFACES-3816
> URL: https://issues.apache.org/jira/browse/MYFACES-3816
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-344
> Affects Versions: 2.2.0-beta
> Reporter: Gerhard Petracek
> Assignee: Leonardo Uribe
>
> for an initial request there is no window-id added to the url.
> (tested with 'url' for javax.faces.CLIENT_WINDOW_MODE)
> -> in case of a page refresh a new window-id will be created and it isn't
> possible to get back the original one. that can also happen with a
> page-refresh after multiple requests, if only ajax requests are used.
> that's a major issue for all scopes based on the window-id.
> it can be done with an initial redirect (default in codi) or js (with html5
> compliant browsers)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
