> I guess the servlet container handles jsessionid transparently.
Yes, coming in (either cookie or in the URI) and setting the cookie; but it
does not normally add it to links in the output from your webapp, that is the
framework or developer's responsibility.
- Tor Iver
--
> jsessionid works
... but leads to lots of boilerplate where you need to rewrite all URLs
targeted at your app's code. I guess Wicket can do that for you, but still...
- Tor Iver
-
To unsubscribe, e-mail: users-unsubscr...@wic