On Nov 8, 2007 11:46 PM, Joshua Jackson <[EMAIL PROTECTED]> wrote:
> Darn it doesn't work. I guess this is a problem with Websphere :(
Igor was referring to putting something like:
<session-config>
<session-timeout>60</session-timeout>
</session-config>
somewhere at the end of your config file.
Anyway, or you sure the session was really expired, or did you (/
Wicket) try to access a page Wicket doesn't think is available? How
about adding a very simple page first, that just prints out the
session id and maybe has some dummy link on it? Like what you can find
in org.apache.wicket.examples.stateless (see the "message" component
in Index).
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
