I hoped to find more flexible solution than writing plenty of dummy get/set code. Now I'm thinking about introducing some field annotation and store/restore field value automatically with component or property path. What is the proper place where page cycle is finish and I can catch the state of properties to store them in session? Or maybe should I create own model which persists state into session? I'm just looking for the best way.
Thanks, Hubert I think you answered your own question, you said you wanted properties that persisted through the session so store them in the session. Either create your own subclass with setters/getters for your properties or you could possibly open up the visibility of Session.setAttribute(String, Object). Or another option might be to use bookmarkable links and output the properties into the URLs for each page like http://host/app/page?itemsPerPage=10&search=theSearch. I think this approach requires stateless pages though? Craig -- View this message in context: http://old.nabble.com/Session-preserved-Page-Page-property-tp26809458p26813775.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
