I tried this on IRC first, but it seems that everybody is busy over
there so i thought i'd try it here :)
It seems that in wicket 1.5, the only way to let 2 Pages (for example, a
page in a modal window + the page that opened that modal window)
communicate with each other (call each others methods, send
intercomponent events, etc.) is via a PageReference.
If i dont use PageReference but just the Page instances themselves it
seems like there are 2 versions of the same page: changes made by the
"popup page" to the "main page" are lost by the time the
WindowClosedCallback.onClose() gets called. I found this out when i was
trying to create a simple yes/no dialog.
Is this the way it is supposed to be?
In 1.4 page objects could communicate directly with each other.
I'm not saying this is a bad thing, just wondering wether this is the
intended behaviour, and if it is, if this shouldn't be documented in the
1.5 migration guide.. and/or other places?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
