Ah, I get it. Yes, you are right too, just never got around rewriting
the login to a stateless form. It has no priority though as our session
never dies.
Regards,
Erik.
Martin Makundi wrote:
Login page is visible, but the form
action="/?wicket:interface=:0:1::::" which is stateful. If my session
dies I will definitely get an error.
Try clicking this link with a new browser that does not have a session
on the site: http://www.tipspot.com/?wicket:interface=:0:1::::
This is what you would get if your browser loaded the page from cache
(or if you let it wait until the session invalidates). Does not look
professional and it is totaly unnecessary, in my opinnion. It should
be possible to handle forms on "virgin" (=no state bound yet)
invocations too.
**
Martin
2009/8/2 Erik van Oosten <e.vanoos...@grons.nl>:
Martin,
I am not sure what you mean. On the site you are referring, the login page
is always visible under /login.
Regards,
Erik.
Martin Makundi wrote:
If I understood correctly, you might find this interesting:
http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT
(looking at the example page referred on the site). Not BEFORE you
CLICK...
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
