[
https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812762#comment-13812762
]
Gerhard Petracek commented on MYFACES-3816:
-------------------------------------------
@dora:
that wasn't the topic. without an initial redirect or including the window-id
in ajax-requests and/or rewriting the url via js, users get unexpected issues
even after the second request (if you only use ajax-requests until a
browser-refresh).
if we would get issues with the tck, we could still do #2 and #3.
i never said that a redirect is the only choice we have.
(it just has less unexpected effects, esp. if you have special logic in your
application.)
> 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)
