Re: Dialog involving multiple pages and a VO: some best practices?

2010-06-07 Thread Joseph Pachod
Igor Vaynberg wrote: obviously you have to know what you are passing around. you shouldnt pass around objects that link to page instances, such as anonymous classes of models. -igor if that's all, then all fine for me quite different from what I had in mind about different references to

Re: SV: Dialog involving multiple pages and a VO: some best practices?

2010-06-04 Thread Joseph Pachod
Wilhelmsen Tor Iver 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

Re: Dialog involving multiple pages and a VO: some best practices?

2010-06-04 Thread Joseph Pachod
Mauro Ciancio wrote: Hi, On Wed, Jun 2, 2010 at 7:43 PM, Joseph Pachod josephpac...@thomas-daily.de 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

Re: Dialog involving multiple pages and a VO: some best practices?

2010-06-04 Thread Joseph Pachod
Igor Vaynberg wrote: 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 ModelDto(new Dto()); and pass that to any page. that way the page does not need to worry

Re: Dialog involving multiple pages and a VO: some best practices?

2010-06-04 Thread Igor Vaynberg
obviously you have to know what you are passing around. you shouldnt pass around objects that link to page instances, such as anonymous classes of models. -igor On Fri, Jun 4, 2010 at 2:04 AM, Joseph Pachod j...@thomas-daily.de wrote: Igor Vaynberg wrote: usually i simply allow pages to take

SV: Dialog involving multiple pages and a VO: some best practices?

2010-06-03 Thread Wilhelmsen Tor Iver
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

Re: Dialog involving multiple pages and a VO: some best practices?

2010-06-03 Thread Mauro Ciancio
Hi, On Wed, Jun 2, 2010 at 7:43 PM, Joseph Pachod josephpac...@thomas-daily.de 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

Re: Dialog involving multiple pages and a VO: some best practices?

2010-06-03 Thread Igor Vaynberg
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 ModelDto(new Dto()); and pass that to any page. that way the page does not need to worry about where the objects