[
https://issues.apache.org/jira/browse/WICKET-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034577#comment-16034577
]
Claudia Hirt edited comment on WICKET-6358 at 6/2/17 12:00 PM:
---------------------------------------------------------------
[~mgrigorov]
Yes, of course you get a new session for a new tab, that's exactly what I
wanted, but my problem is, as described:
{quote}But I think somehow the session gets lost when switching pages (*in the
same tab*).{quote}
Please tell me whats missing concerning steps to repeat:
{quote}After login you can switch between two pages. Using your sample
implementation for making tabs independent, the session seems to get lost on
the second page.{quote}
- When starting my application there's a Login Page
- Klick on Login -> you get to "home page"
- There's a label on each page which tells you, if the session exists
- Klick Link on HomePage to get to "another page"
- You get kicked out of your session back to Login page, instead of going to
"another page". "another page" cannot be reached.
Sorry, if my explanation wasn't enough, but I tried my best to build a
self-explaining application.
was (Author: claudia hirt):
[~mgrigorov]
Yes, of course you get a new session for a new tab, that's exactly what I
wanted, but my problem is, as described:
{quote}But I think somehow the session gets lost when switching pages
(*strong*in the same tab*strong*).{quote}
Please tell me whats missing concerning steps to repeat:
{quote}After login you can switch between two pages. Using your sample
implementation for making tabs independent, the session seems to get lost on
the second page.{quote}
- When starting my application there's a Login Page
- Klick on Login -> you get to "home page"
- There's a label on each page which tells you, if the session exists
- Klick Link on HomePage to get to "another page"
- You get kicked out of your session back to Login page, instead of going to
"another page". "another page" cannot be reached.
Sorry, if my explanation wasn't enough, but I tried my best to build a
self-explaining application.
> Possibility for each browser tab to have independent wicket session
> -------------------------------------------------------------------
>
> Key: WICKET-6358
> URL: https://issues.apache.org/jira/browse/WICKET-6358
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 8.0.0-M5
> Reporter: Martin Makundi
> Assignee: Martin Grigorov
> Attachments: Wicket_Quickstart_7.zip
>
>
> Here are a couple of discussions on the topic:
> https://myfaces.apache.org/orchestra/myfaces-orchestra-core/multiwindow.html
> http://stackoverflow.com/questions/368653/how-to-differ-sessions-in-browser-tabs
> http://stackoverflow.com/questions/4970004/support-multiple-browser-tab-session-j2ee-web-application
> Currently in wicket if user wants to safely use two browser windows in the
> same application, they must login from different browsers (or use some
> suitable browser-specific private browsing mode).
> We would like to add functionality into wicket to allow:
> - automatic detection of new browser tab
> - configuration option which would keep independent wicketsession for each
> browser tab (initially clone from wicketsession of window that opened new tab)
> - possible solution: pagemap and wicketsession could go hand in hand, each
> pagemap with its own wicketsession to keep them insulated
> We'll start working on this immediately, all suggestions welcome.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
