> 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.
Like Igor said, calling dirty when you set a value should do the trick. If it doesn't it's a bug :) > 2) The location quoted for the live examples > (http://wicketstuff.org/wicket13/) is the one I was looking at, however for > the specific example "stateless", it is not possible to view the source code > and/or page files "live". Not sure how the site is maintained, but perhaps > a download link could be added on the examples page to the build that the > live examples demonstrate, by default. I've got the files now however, so > thanks again! Ah, ok. That example doesn't use the header all the other examples use because that header would make it statefull :) Could probably be fixed, but atm it's a bit too much trouble. Cheers, Eelco ------------------------------------------------------------------------- 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
