Hi, On Wed, Jun 2, 2010 at 7:43 PM, Joseph Pachod <[email protected]> wrote: > I've recently been wondering about the following use case: an instance of Foo > class, > used as a detached value object, is edited in a FooEditPage. For some > reasons, let's > say this page then needs to launch dialogs spanning over different pages. > Each of > these pages could then change some fields of the VO being passed around.
Have you taken a look to wicket-wizards? http://www.wicket-library.com/wicket-examples/wizard/ > in fact, I mainly wonder about the pages' serialization... are there some > pitfalls to avoid ? If you have to track the object's state through several pages, you'll need a serializable object, because reloading it using a LDM in every request will throw away all the changes made before. So, your Foo must implement Serializable, or you could create some proxy object that tracks the changes and when the user finish the editing process, apply the changes to the real model object. On Thu, Jun 3, 2010 at 9:19 AM, Wilhelmsen Tor Iver <[email protected]> wrote: > Sharing between pages is easier done by placing it in the Session which is > accessible > from all of them. I think that storing a model object in the session is not a good choice; if the user opens two browser windows, what will happen? Regards. -- Mauro Ciancio <maurociancio at gmail dot com> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
