Fwd: Re: [Wicket-user] problem with session invalidation and back button

[Jaime De La Jara]

Hi, I finally fixed it, the problem was that I set a response page after invalidating
the session, I commented the line and also redefined the PageExpiredErrorPage
and it worked!.

Thanks.

Jaime.

Jaime De La Jara <[EMAIL PROTECTED]> wrote:

Date: Tue, 28 Mar 2006 14:01:39 -0800 (PST)
From: Jaime De La Jara <[EMAIL PROTECTED]>
Subject: Re: [Wicket-user] problem with session invalidation and back button
To: wicket-user@lists.sourceforge.net

But, in the original case it does not show the page expired page, but shows an
exception. I think that I missing something here. I commented the
 session.invalidate code and in this case when I resubmit the form, since the form
 exists, the authentication code is executed and the login page displayed. Then
how can one invalidate the session and not have trouble with the browser's back
button?.

Jaime.

no because this is an Page expired session. Nothing gets 
created because if you press a submit button on a page.
Then that page must be there. Must be targetable. So you
get an page expired page.
 What you could do is set youre default expired page:
 void setPageExpiredErrorPage(final Class pageExpiredErrorPage);
 
 
 
 On 3/28/06, Jaime De La Jara <[EMAIL PROTECTED]> wrote:
 >
 > Not exactly, when I'm in the login page I press the back
 > button and return to the home page
 (that seems ok since 
 > it was the last page), then in the home page I use a 
 > submit button but since the session was invalidated,
 > wicket can not find info about the form being submitted. 
 > All the problem reduces to this : How can I intercept the
 > requests so I can check the session status (I
 reimplemented 
 > the isInstantiationAuthorized(Class componentClass) of 
 > the IAuthorizationStrategy interface to check for
 > authentication info but it does not work in this case).
 >
 > Thanks.
 >
 > Jaime.

Johan Compagner <[EMAIL PROTECTED]> wrote:

Let me get it straight first.

You where on youre homepage
then you click on something
where you invalidate the page and redirect to a login page.
Then on that login page you go back to youre homepage
and you expect the homepage to be there?

You invalidated the session and all its pages. So you can't go back.
If you want this behaviour then just don't invalidate the session. But clear you login info.

johan

On 3/27/06, Jaime De La Jara <[EMAIL PROTECTED]> wrote:

Hi, I have included a close session link in the home page of my application (in one of the constructors), and in the onClick method of the link I invalidate the session and throw a RestartResponseException to the login page, but after I close the session using the link and press the back button in the login page I got the home page as it should be, but when I press a submit buttom in the home page, I get a WicketRuntimeException, since the form component is not existant in the page. What can I be doing wrong?.

Thanks in advance.

Jaime.

---

New Yahoo! Messenger with Voice. Call regular phones from your PC for low, low rates.

---

New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

---

Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.