[ 
https://issues.apache.org/jira/browse/MYFACES-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966426#comment-13966426
 ] 

Leonardo Uribe commented on MYFACES-3881:
-----------------------------------------

I don't think it can be a bug. F5 means a new request is done, which also means 
a new client window should be generated because there is no way to share info 
between those request. They are completely independent.

As is right now there are two modes for client window stuff:

- "url" mode: (default by spec) uses a query param, like MyFaces Orchestra 
conversationContext
- "client" mode: a prepocessor page with some javascript generates the window 
id in the client.

There is no perfect solution for client window problem, but the api is flexible 
enough to allow alternate implementations, so if you have an idea about how to 
do it we can discuss it and include it as a new mode.

> CLIENT_WINDOW_MODE generates new windowid even if one exists
> ------------------------------------------------------------
>
>                 Key: MYFACES-3881
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3881
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.2.2
>         Environment: java 7, tomcat 7.0.50
>            Reporter: Rene O
>         Attachments: jsftest22.zip
>
>
> If you use @ViewScoped beans and activate CLIENT_WINDOW_MODE (url or client) 
> a page refresh generates a new windowid although the application in the 
> current browser window already has a windowid.
> I think a new windowid should only be generated, if no windowid exists, e.g. 
> open new window or tab with the same url.
> <context-param>
>    <param-name>javax.faces.CLIENT_WINDOW_MODE</param-name>
>    <param-value>url</param-value>
>    <!--client doesn't work too-->
> </context-param>
> A testcase is attached.
> call url: http://localhost:8080/jsftest22/mypage.jsf
> Fill some values into field
> Press F5 to refresh the page
> => new windowid is generated => inputdata is lost, because a new @ViewScoped 
> bean was created



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to