If it's implemented in 1.4 then it's enough for me, guess I will migrate
to that version then.
Thanks for help, everyone involved.
David Matousek
Carlo Camerino napsal(a):
i have verified that this fix has already been implemented in 1.4
is there any chance that this would be backported to the 1.3 branch?
from what i understand, there would be no more releases for the 1.3 is this
correct?
2009/11/21 Igor Vaynberg <igor.vaynb...@gmail.com>
http://www.wicket-library.com/wicket-examples/ is running a very old
version, may even be 1.2.x.
you should use wicketstuff.org/wicket14
-igor
2009/11/20 David Matoušek <david.matou...@monetplus.cz>:
It was happening to me on Wicket examples page too. Especially on
AjaxFallbackDataTable Example.
<?wicket:bookmarkablePage=:org.apache.wicket.examples.repeater.AjaxDataTablePage>
I just checked it but now it seems to be working correctly. What version
of
Wicket are examples on url:
http://www.wicket-library.com/wicket-examples/
running and were they changed lately?
I am using 1.3.6 so maybe it was fixed in 1.4.x versions.
David Matousek
I do not have that problem: if session expires any action the user does
triggering a server round trip, AJAX or not, on a protected page
redirects
me to the login page... Can you post more details?
Best,
Ernesto
2009/11/20 Carlo Camerino <carlo.camer...@gmail.com>
yes we also have this prob lem.... For example i use a wicket in
dicating ajax button in our logi n page. If thne user doesn t click a
link that moves a page he will not be able to k now that the session
has i ndeed expired. The screen o ly shows the rotating image but
nothing happens. but if i use a normal submit li nk, im immeddiately
redirected..
Some clients didnt mind it bbut some clients do
thanks
On 11/20/09, Igor Vaynberg <igor.vaynb...@gmail.com> wrote:
afair any ajax interaction on an expired page causes the same reaction
as a non-ajax interaction - going to the page expired page. open a bug
with a quickstart if that is not the case.
-igor
2009/11/19 David Matoušek <david.matou...@monetplus.cz>:
Hi,
I have a problem with ajax behavior, that i use to fill various
dropdowns
by
data from database.
When session expires(user was inactive), non-ajax controls correctly
redirect me to some kind of Error page. Thats correct.
Components that have defined ajax behavior to update another
components
don't redirect, and doesn't update another components either.
Is that Wicket feature, or a bug? Can components with ajax behaviors
be
forced to redirect to error page on session expire like non-ajax ones
do?
Any suggestions?
Thanks for reply
David Matousek
--
Tato zprava byla prohledana na vyskyt viru
a nebezpecneho obsahu antivirovym systemem
MailScanner a zda se byt cista.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Tato zprava byla prohledana na vyskyt viru
a nebezpecneho obsahu antivirovym systemem
MailScanner a zda se byt cista.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Tato zprava byla prohledana na vyskyt viru
a nebezpecneho obsahu antivirovym systemem
MailScanner a zda se byt cista.
