Yes, it is encodeURL that does this; if you forget to do encodeURL on
your links, your webapp won't work without cookies. This is a common
problem in plain JSP/ model 2 frameworks.
However, when the client has cookies enabled, jsessionid usually goes
away after the first request. That must be the container that decides
that, probably in it's implementation of the servlet API.
Eelco
Matej Knopp wrote:
Juergen Donnerstag wrote:
jsessionid is inserted by the container automatically once a session
has been created. It is not wicket.
I believe it's encodeURL method of HttpServletResponse that inserts
the jessionid in URL. The container itself has AFAIK no idea what in
the response body is url and what's not.
-Matej
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
