Hi David,

I just attached a demo app with a behavior to
https://issues.apache.org/jira/browse/WICKET-4308 that implements the
requested functionality.
Please try it and give feedback.

On Thu, Apr 26, 2012 at 8:30 AM, David Rain <[email protected]> wrote:
> Hello Martin!
>
> I do not use it right now but I would like to. I knew it was there because
> I've studied API and sources of Wicket. But it was in time we used Wicket
> 1.4 and I knew I came across this onNewBrowserWindow method and many classes
> implemented it
> http://wicket.apache.org/apidocs/1.4/index.html?org/apache/wicket/markup/html/INewBrowserWindowListener.html
>
> Now it is gone (we use Wicket 1.5.5 now). We have an application that is
> completely AJAX like. Only 2 page (login & main) a the content inside is
> switched (via replace methods and AjaxRequestTarget#add). But - as far as
> security is concerned - we have to logout user and destroy session when he
> opens another window or tab. That's a rule we cannot break. So I need some
> detection of "new window opened" event.
> I use logout and session invalidation in onConfigure now - the main page is
> rendered only once, everything is made via AJAX calls then. Thus another
> render attempt means that user opened new window or tab (but he could have
> also pressed F5 -> and it would end in logout too, but in this case we do
> not want it - that's why I said it's just a temporary workaround).
>
> Thanks for any ideas.
>
> David
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-new-browser-window-support-detection-tp4582538p4588927.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to