usually i simply allow pages to take models of whatever it is they need, just like any other component. in case of a dto being passed around you can simply use the default model: new Model<Dto>(new Dto()); and pass that to any page. that way the page does not need to worry about where the objects comes from or how to store it.
-igor On Wed, Jun 2, 2010 at 3:43 PM, Joseph Pachod <[email protected]> wrote: > hi > > 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. > > how would you handle the Foo instance being given through ? > > in fact, I mainly wonder about the pages' serialization... are there some > pitfalls to avoid ? > > on a side note, for the "return page" requirement of the dialog, I would just > give the calling page on the next one. Something like setResponsePage(new > DialogPageX(this, ...)); > > is this ok ? > > thanks in advance > best regards > joseph --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
