[
https://issues.apache.org/jira/browse/DELTASPIKE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142141#comment-14142141
]
Thomas Andraschko commented on DELTASPIKE-729:
----------------------------------------------
Currently the workflow is:
1) new tab - request without dswid
2) initial redirect with generated dswid
3) rendering view
4) windowhandler.js detects a null window.name ->
- set window.name to tempWindowId
- redirect to the same view without dswid to get actually sure that we get
an valid and new windowId
5) initial redirect + generate a new dswid again
6) rendering view
7) windowhandler.js detects the "tempWindowId" window.name and takes the dswid
as new window.name
Possible solution:
on 1) we can store a cookie (flash is too early!) to remember the initial
redirect
on 2) we can render a parameter to the client side, that this windowId is valid
as it was generated from the last request/initial redirect
Workaround:
disable initial redirect
> f:viewAction is executed twice with LAZY window handling mode
> -------------------------------------------------------------
>
> Key: DELTASPIKE-729
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-729
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 1.0.3
> Reporter: Thomas Andraschko
> Assignee: Thomas Andraschko
> Priority: Minor
> Fix For: 1.0.3
>
>
> If you define h:head within your site and use ds:windowId
> (ClientWindowRenderMode.LAZY), then f:viewAction is called twice (2 window
> ids are generated)
> This was already fixed since 0.7 but broke the lazy new window detection.
> i will not try to find a workaround via flash scope.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
