I guess he meant that this is very common use case and that's why we
believe it is an error in your code.
Please create as simple as possible application that manifests the
problem [1] and attach it to a ticket in the bug tracking system [2].
[1] To create a simple application you may use Wicket Q
1842946.n4.nabble.com/Consecutive-AJAX-operations-lead-to-Page-Expired-tp2286087p2287076.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional c
ontext:
> http://apache-wicket.1842946.n4.nabble.com/Consecutive-AJAX-operations-lead-to-Page-Expired-tp2286087p2286087.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e
LW,
using the same steps, we get the PageExpiredErrorPage.
Any and all ideas are welcomed.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Consecutive-AJAX-operations-lead-to-Page-Expired-tp2286087p2286087.html
Sent from the Wicket - User mailing list archive at
