[
https://issues.apache.org/jira/browse/DELTASPIKE-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290697#comment-15290697
]
Thomas Andraschko commented on DELTASPIKE-1148:
-----------------------------------------------
The describe the problem:
GET test
1) server: no active windowId, therefore the windowhandler will be streamed
and "uninitializedWindowId" will be passed as windowId
2) client: if the windowId == uninitializedWindowId and the window.name is
not initialized, will will request a new windowId from the server
GET test?dsrid=590
3) server: generates a new windowId and streams the windowhandler again
4) client: applies windowId to window.name and redirects to the actual view
A solution would be to pass a flag from 2) to 3) that the windowId is
unitialized on client and on server
> Reduce redirects in CLIENTWINDOW mode when opening a link in a new tab
> ----------------------------------------------------------------------
>
> Key: DELTASPIKE-1148
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1148
> Project: DeltaSpike
> Issue Type: Improvement
> Components: JSF-Module
> Reporter: Bernhard Hablesreiter
>
> We were testing the new DeltaSpike CLIENTWINDOW mode with
> "ClientWindowTokenizedRedirect" option enabled and noticed that if we open a
> link in a new tab (get-request), two redirects happen, e.g:
> GET test
> GET test?dsrid=590
> GET test?dswid=-3402&dsrid=716
> The windowhandler.html file is streamed twice in this scenario.
> Maybe the redirection can be limited to one in those cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
