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]
