[
https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812398#comment-13812398
]
Leonardo Uribe commented on MYFACES-3816:
-----------------------------------------
Is it really broken? or we are dealing with an specific non frequent case? what
could be wrong? The code was taken directly from CODI, so is CODI broken in as
well?
If a new windowId is created in a page refresh, it doesn't matter, because if
it reuse the previous one or the new one, the state in session will be just the
same. Why do we have to go back to the previous one that is not being used?.
The worst that can happen is create a bean twice (one in a previous context and
the second in the current context).
It is still looks like an implementation detail of the specific used mode. If
the user care about that, just add a new mode and problem solved.
> 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)
