As I understand - the correct way is change usage PageCreator to setContent:)
Thank you very much for all your answers!!!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484858.html
Sent from the Users forum mailing list
ure about setting of the content on the fly
This will work. We do this in our app. There is one modal window which
content is dynamically loaded depending on the clicked link.
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serializati
context:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484792.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
meone will come up with a simpler
> solution
the solution is already there - ModalWindow.setContent(aPanel)
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484708.html
> Sent from the Users forum m
Thanks for your answer,
of course session is not so simple as local variable - but it one of the
solution
Maybe in next releases of wicket someone will come up with a simpler
solution
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization
ou pass a final object to an
inner class) but I think
the safest way is to keep such objects in the session. You can share
objects (or even better models) between components in a page, but as
you already read about it this is not the case when you share between
pages.
So
- solution 1 - put the objec
cases I should) use local variables.
Can anyone give advice - how to simplify usage of modal windows in such
cases?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-and-Serialization-tp4484547p4484547.html
Sent from the Users forum
