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 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.

As answered to Maruo, is there any "dragon lurking" there, with some return page de serialized instance's references pointing to some other reference that the one behind the current model being given around ?

I was somehow under the impression it was kind of risky...

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to