[
https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812406#comment-13812406
]
Gerhard Petracek edited comment on MYFACES-3816 at 11/3/13 4:06 PM:
--------------------------------------------------------------------
there is nothing in the spec./javadoc which mandates that we aren't allowed to
do it correctly. if no window-id was found, it is required to create a new id.
but there is no statement (or restriction) about the steps afterwards.
that can't be a compatibility-issue - otherwise we would have to implement all
other mojarra issues as well.
was (Author: gpetracek):
there is nothing in the spec./javadoc which mandates that we aren't allowed to
do it correctly. if no window-id was found, it is required to create a new id.
but there is no statement (or restriction) about the steps afterwards.
that can't be an issue with compatibility - otherwise we would have to
implement all other mojarra issues as well.
> missing window-handling for initial requests
> --------------------------------------------
>
> Key: MYFACES-3816
> URL: https://issues.apache.org/jira/browse/MYFACES-3816
> Project: MyFaces Core
> Issue Type: Improvement
> 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)
