[jira] [Commented] (MYFACES-3881) CLIENT_WINDOW_MODE generates new windowid even if one exists

["Thomas Andraschko (JIRA)" <de...@myfaces.apache.org>]

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

Thomas Andraschko commented on MYFACES-3881:
--------------------------------------------

I would close it for now.
DeltaSpike delivers much better CLIENTWINDOW modes and it can be easily used.
We should not do the same in MyFaces Core as DeltaSpike also works fine for Mojarra.
I think the JSF API is fine here, just doesn't cover all cases. We may try to include the DeltaSpike modes into JSF.next.
WDYT?

> 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, jsftest22_new.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.4.14#64029)