Try giving your modal page a reference to the outer page object, and not just a model within it. This way serialization of the modal page will encounter the outer page and update its pagemap entry. I don't know what's up with 1.5, but with certain request patterns we found this necessary even in 1.4.
On Wed, Sep 21, 2011 at 4:44 AM, Sotil Bertanzetti, Matteo < mso...@gencat.cat> wrote: > Is there another option?, I would have to do a lot of changes to implement > Panel backed ModalWindow. > > Maybe I stay on wicket 1.4 for a while. > > Matteo Sotil > > -----Missatge original----- > De: Martin Grigorov [mailto:mgrigo...@apache.org] > Enviat: miércoles, 21 de septiembre de 2011 13:19 > Per a: users@wicket.apache.org > Tema: Re: ModalWindow problem > > On Wed, Sep 21, 2011 at 12:25 PM, Sotil Bertanzetti, Matteo > <mso...@gencat.cat> wrote: > > Thanks for responding. > > > > I'm using a dynamic model (PropertyModel) but it doesn't work either. > > For me it's an important loss of functionality. I use it on modal > > windows, to show a search page (with TabbedPanel, list with > > pagination...) and select one register; could you please suggest me some > > alternative?. > > Use ModalWindow backed by a Panel instead of a Page. It is much more > stable. > There are many tickets for ModalWindow backed by a Page. > > > > > Thank you. > > > > Matteo Sotil > > > > -----Missatge original----- > > De: Andrea Del Bene [mailto:adelb...@ciseonweb.it] > > Enviat: martes, 20 de septiembre de 2011 18:16 > > Per a: users@wicket.apache.org > > Tema: Re: ModalWindow problem > > > > Hi, > > > > we dealt this topic in this issue: > > > > https://issues.apache.org/jira/browse/WICKET-3809 > > > > Basically starting from Wicket 1.5 you can't share static models between > > > > pages. > >> Hello. > >> > >> > >> > >> I have a problem with ModalWindow in wicket 1.5.0. > >> > >> I create a ModalWindow from a page, and that modal window changes > >> original page's model; some textfields should change their value > >> according to model change, but they not; in fact seems as if model had > >> not really changed. ModalWindow's content is a page, not a component; > > if > >> I use a component as content, it works, but I need it to be a page. > > This > >> worked correctly on wicket 1.4.18. > >> > >> > >> > >> Matteo Sotil > >> > >> 935526855 > >> > >> mso...@gencat.cat > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
