What you describe i already replied
Thats the hybrid approache if pages can be stateless then wicket can
generate already urls that can generate the page again if expired and
the call the event
On 12/06/2009, Martin Sachs wrote:
> I wonder why this is so a big problem. On bookmarkable Webpages (e
I wonder why this is so a big problem. On bookmarkable Webpages (e.g.
Productpages) the user dont need to login and the session can destroyed
via timeout. Each Ajax-Request throw would throw a PageExpiredException.
This is the worst thing in wicket, IMHO.
My tryout was the following in a quickstar
Yes if you dont want to have page expires you could try to use
bookmarkable pages all the way and use the hybrid coding to get mixed
book/session pages.
Or store something in the db record the last page for every user...
On 12/06/2009, Jeremy Thomerson wrote:
> the path is stored in the session,
Or implement a "remember me" feature in the request cycle.
--
Jeremy Thomerson
http://www.wickettraining.com
On Fri, Jun 12, 2009 at 2:38 PM, Jeremy
Thomerson wrote:
> Just lengthen the session timeout - how to do this depends on your
> servlet container.
>
> --
> Jeremy Thomerson
> http://www
Just lengthen the session timeout - how to do this depends on your
servlet container.
--
Jeremy Thomerson
http://www.wickettraining.com
On Fri, Jun 12, 2009 at 2:37 PM, Christopher L
Merrill wrote:
> Jeremy Thomerson wrote:
>>
>> the path is stored in the session, so as long as your app server
Jeremy Thomerson wrote:
the path is stored in the session, so as long as your app server
reloads existing sessions on restart, it should (iirc). however, in
your dev environment, the app server probably blows away sessions
hr, i just re-read and realized that you said this is for the
PageEx
the path is stored in the session, so as long as your app server
reloads existing sessions on restart, it should (iirc). however, in
your dev environment, the app server probably blows away sessions
hr, i just re-read and realized that you said this is for the
PageExpired which is typical
Wow, I hope it's really that easy!?!
Should this work through an appserver restart? E.g. if I
1) login to the app
2) restart the app server
3) click a page link in the browser
Should this work? It didn't for me. Based on my limited understanding of
how wicket works and stepping into the code,
in your login form submit, call continueToOriginalDestination()
onSubmit() {
if (false == continueToOriginalDestination()) {
setReturnPage(SomeOtherPage.class);
}
}
--
Jeremy Thomerson
http://www.wickettraining.com
On Fri, Jun 12, 2009 at 1:45 PM, Christopher L
Merrill wrote:
> I've changed o
I've changed out PageExpiredErrorPage to be the login page for our app.
Does wicket have any support built-in to help return the user to where
they were after re-authenticating?
From my modest understanding of Wicket, it would need to be a bookmarkable
page, which will be ok for a good percentage
10 matches
Mail list logo
