I found a JIRA issue was filed for this a while back:
https://issues.apache.org/jira/browse/WICKET-1703
...but it hasn't been addressed yet...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PR
;> >
>>> >
>>> > --
>>> > Jeremy Thomerson
>>> > http://www.wickettraining.com
>>> >
>>>
>>>
>>>
>>> --
>>> WBR, kan.
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>
>
>
> --
> WBR, kan.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/continueToOriginalDestination-and-POST-tp20704326p20711992.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yes, I am talking about timeouts.
Actually... Maybe I want from wicket more than it was designed for. In
some cases state of web-application could be on client-side and
doesn't need to be in server-side session, only exception is
auth-data. And I don't like fact that user faces with "page expired"
You could add a feature request (and a patch?).
My point was don't let them start on the form until they are signed in if
being signed in is required for submitting the form. This just makes sense.
Or, if what you're saying is that they are timing out while working on the
form, add an ajax updat
A user has started to work with the form, then was distracted for 20
minutes, then he comes back and presses "submit".
Is it difficult to store PageParameters too?
2008/11/26 Jeremy Thomerson <[EMAIL PROTECTED]>:
> They shouldn't be able to access the bookmarkable page with the form (or,
> access
They shouldn't be able to access the bookmarkable page with the form (or,
access the page, but have the form hidden until signed-in). For
continueToOriginalDestination, IIRC, Wicket just stores the URL, so you
can't go back to a POST.
On Wed, Nov 26, 2008 at 10:27 AM, kan <[EMAIL PROTECTED]> wrot
I have a site which requires authentication. I've made it via
@AuthorizeInstantiation.
Works well. But if a bookmarkable page has a with method POST,
and user presses "submit" after timeout, it redirects him to SignIn
screen. After successful login the site redirects back (usinig
continueToOrigina
