> Thanks guys for all the help, you are amazingly responsive. Now I feel bad
> and have to be more responsive with open source project I manage 8-). You
> are setting the example!
Heh, cool. Which one is that?
> BTW, I came with solution after reading the first chapter of Wicket In
> Action.
And
I added:
setResponsePage(MyAppHome.class);
after session.invalidate();
, and that fixed the problem.
Thanks guys for all the help, you are amazingly responsive. Now I feel bad
and have to be more responsive with open source project I manage 8-). You
are setting the example!
BTW, I came with s
> After re-login when I get Page Expired, the url is:
> http://localhost:8080/MyApp/app/?wicket:interface=:0::
Yeah, that's a reference to an already rendered page. Try to find why
it tries to render that. You could try setting a break point in the
Wicket filter and go from there for instance, and
Oops, never mind. I see the new users list on Nabble. Just clicked on wrong
one. Sorry for the noise.
Eelco Hillenius wrote:
>
> Btw this user list is about to shut down. Please subscribe to
> [EMAIL PROTECTED] (by sending an email to
> [EMAIL PROTECTED]) and have future discussions there.
>
Thanks Eelco, I already did. But I like using Nabble so that is how I got to
this mailing list, and thought it is the new mailing list. Do you know if
[EMAIL PROTECTED] is available on Nabble?
Lubos
Eelco Hillenius wrote:
>
> Btw this user list is about to shut down. Please subscribe to
> [EM
After re-login when I get Page Expired, the url is:
http://localhost:8080/MyApp/app/?wicket:interface=:0::
igor.vaynberg wrote:
>
> hrm, i dont see how /MyApp/app can ever cause a page expired error because
> it is a bookmarkable url and so a new instance of page is always created.
> i
> would
Btw this user list is about to shut down. Please subscribe to
[EMAIL PROTECTED] (by sending an email to
[EMAIL PROTECTED]) and have future discussions there.
Eelco
-
This SF.net email is sponsored by: Splunk Inc.
Still greppi
> so you do not think that session.invalidate() can cause the page to expire?
Only if you try to render a page that is part of that old - now
invalidated - session. Make sure Wicket doesn't try to do that (e.g.
check whether the authorization strategy doesn't try to do another
redirect).
Eelco
-
Igor,
so you do not think that session.invalidate() can cause the page to expire?
I do not know if it makes difference, but I use Acegi, and regular login.jsp
page for login page,
not a Wicket managed page (I did not figure out how to use Wicket managed
login page with Acegi).
Lubos
igor.vaynb
hrm, i dont see how /MyApp/app can ever cause a page expired error because
it is a bookmarkable url and so a new instance of page is always created. i
would debug the request cycle and see why it cannot find the page, seems
very strange to me
-igor
On 7/28/07, lubosp <[EMAIL PROTECTED]> wrote:
>
Igor,
after login page (login.jsp) it is redirected to /MyApp/app which goes to my
wicket home page, and that one is expired.
Is it possible that I am missing something on logout action?
Is it enough to do session.invalidate()?
Note, it works properly the first time, only after I log out and t
what url causes the page expired page?
-igor
On 7/28/07, lubosp <[EMAIL PROTECTED]> wrote:
>
>
> Hi guys,
>
> my first wicket mailing list post. I just started using Wicket couple gays
> ago (after using Tapestry and ZK), and I have to say, I am impressed.
> Congratulation to great framework!
>
Hi guys,
my first wicket mailing list post. I just started using Wicket couple gays
ago (after using Tapestry and ZK), and I have to say, I am impressed.
Congratulation to great framework!
I have tried to port my application, which uses Acegi Spring security to
Wicket. I managed to port the core
13 matches
Mail list logo
