I already have several Wicket applications deployed, some that don't require
a session (all extranet - non-signin, bookmarkable url stuff), and one large
one that uses the session extensively.
Now, I just deployed a site last night for testing that is a backend
administration site, which obviously requires a session for the user to sign
in, etc. But, on every bookmarkable link, it appends the jsessionid (not
just the first link like normal), and on non-bookmarkable links (i.e.
http://admin.theatdgroup.com/app/?wicket:interface=:15::::), it doesn't
append the jsessionid, but I get Page Expired (and this is without the page
actually being expired).
I'm running the latest, built-from-svn version of Wicket. This is also my
first stateful Wicket app to deploy on Linux (the others are on Windows).
I'm using Tomcat, and have made sure that the sessions last 60 minutes. It
is behind Apache, using mod_proxy, just like all of the other Wicket apps
that I have deployed.
I know there's just a setting I'm missing somewhere... any ideas?
Thanks!
Jeremy Thomerson
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
