deltaspike-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Flanigan <sflan...@redhat.com>
Subject Re: JSF: dswid=tempWindowId for every duplicated tab in Chrome
Date Fri, 26 Jun 2015 00:35:46 GMT
Thanks Thomas.  It happens with Firefox and JSF Playground too.

I've submitted https://issues.apache.org/jira/browse/DELTASPIKE-939


On 2015-06-26 03:14, Thomas Andraschko wrote:
> Hi,
> 
> i think no-one tested the "Duplicate Tab" behavior. It's also new for me as
> Firefox user.
> Would you please create a issue?
> It would be great if you could provide a example or check if it does occur
> with the jsf-playground (which is avaiable in the deltaspike git repo).
> 
> Regards,
> Thomas
> 
> 2015-06-25 10:15 GMT+02:00 Sean Flanigan <sflaniga@redhat.com>:
> 
>> (Warning: I'm very new to DeltaSpike!)
>>
>> I am using ClientWindowRenderMode.CLIENTWINDOW and a JSF page with
>> <ds:windowId/>, and a ViewAccessScoped action bean which prints its
>> identity whenever its corresponding commandButton is clicked.
>>
>> If I navigate via that button, or h:link, or <a href>, everything works
>> as I expect: the dswid is preserved, and the bean has the same identity
>> within the same browser tab.  And if I use middle-click to open a new
>> tab, each tab gets a new identity (new dswid) and a new instance of the
>> bean.
>>
>> The problem happens when I use Chrome's "Duplicate Tab" feature.
>> Whenever I clone a tab that way, I get (after a redirect) a new tab with
>> dswid=tempWindowId, and each of these tabs is sharing the same instance
>> of my ViewAccessScoped bean.
>>
>> How can I ensure that duplicated tabs get their own identity, instead of
>> sharing "tempWindowId"?
>>
>> Regards,
>>
>> Sean.
>>
>> --
>> Sean Flanigan
>>
>> Principal Software Engineer
>> Globalisation Tools Engineering
>> Red Hat
>>
>>
> 


-- 
Sean Flanigan

Principal Software Engineer
Globalisation Tools Engineering
Red Hat


Mime
View raw message