Re: stateless resources vs. no cookies

2012-06-14 Thread Martin Grigorov
Hi, Wicket creates temporary o.a.w.Session object only if Session.get() is called during the request lifecycle. Until you call Session().get().bind() no javax.servlet.HttpSession will be created and Wicket's Session will be garbage collected at the end of the request processing. On Wed, Jun 13,

stateless resources vs. no cookies

2012-06-13 Thread Jan Loose
Hi, I found this problem in Wicket 1.4.20 if cookies are disabled. If there is used a stateless resource then no jsessionid is rendered. It is removed on the line 390 of the class WebRequestCodingStrategy. I hope this is OK. Once the browser makes a request to this resource, then there is