[
https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812436#comment-13812436
]
Leonardo Uribe commented on MYFACES-3816:
-----------------------------------------
I know the std. mode is not the best for production, but is not useless at all.
We needed a minimal mode that can be suitable for test features like faces
flow, the new view scope, the fixed state manager and others. Without this
mode, it is not possible to build proper compatibility tests for all these
features.
So, the spec was done to allow multiple implementations, but providing a
minimal mode that can be suitable for testing, or even for production if you
don't care about those issues.
It looks like a random behavior? Maybe yes. Can we do it better? Yes, of
course, we can write as many modes as we want. But it is too late to change the
default mode. Fortunately there is a way out, because one thing we had clear
since start was that there is no perfect solution for this stuff, and we don't
have clear which mode is the best one (no other web framework has).
> 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)
