Thanks Gabor. I had the same idea. I'll try it soon and leave here a message how it works. Btw I think many people would appreciate an article about wicket application architecture.
Fero Gabor Szokoli wrote: > > On 8/28/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: >> well, what wicket does is version the state if you keep it inside its >> model, >> so it all Just Works. But because you are keeping your state outside of >> wicket you have to build your own versioning mechanism, or remove your >> state >> machine and use wicket. > > Assuming the SM state is not too big, you could keep it in your base > page object. > Then it would get replicated along with the page in the cache, wouldn't > it? > Make sure it is serialisable. > Or to get bookmarkable pages, keep it in the PageParameters. > > Except for the variables which truly belong to the session, like > logged in user, of course. > > More experienced people please correct me if I'm wrong. > > > Gabor > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Presentation-and-application-logic-separation-tf4341077.html#a12392226 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
