On 7/24/07, spencer.c <[EMAIL PROTECTED]> wrote: > > Thanks Eelco, that did the trick. > > Couple of follow up questions/comments that anyone can field: > 1) I understand why you would want a stateless application, however I don't > understand why you would ever want your session to be regenerated on each > request if during the request you specifically set a session value. It > seems like once you set a session value, the session should become bound. > Is there a logical reason this isn't the case, or is it just a > technological/implementation reason? I'm just trying to understand this > better. It's because wicket uses the session object internally, and it can't function without having at least a temporary session. While I understand this is not the most intuitive solution for users, changing this behavior would require a massive change to wicket, something which we can't do now due to the 1.3 release.
If you have changed your session state you might want to call the bind() method on session explicitly. -Matej ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
