Hi. I have the situation, where more than one page is referencing the same parent model - wrapped and not. I use thickbox (somewhat like modal window), and display separate pages in the thickbox using iframe. So you get like ParentPage ->creates-> SubTBPage.
What I do want here, is for all those pages share the same model in this fashion: ParentPage (uses model_1) -> createsPageForThickboxIframe -> SubTBPage (uses model_1.1(wrapping model_1)). In case to make it functional - so the child model objects (MO) (of model_1.1) would use parent wrapped MO (of model_1), I keep the reference to parent (wrapped) model in child MO. The problem is, that in the end two pages starts using different MO's - so obviously because of the serialization. Are there any best practices for such scenario? How could I create Model objects hierarchy, and pass that around without being afraid of hidden traps? I guess I shouldn't reference Models in my model objects, but then, how would I reference model objects from my wrapped model. Should this logic go to model itself? Thanks, Vytautas --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
