Sorry, I said that wrong: Basically, if PageA modifies something in PageB, PageA needs to have a reference to PageB itself; a reference to an object in *PageB* is generally not sufficient to update the page map entry for *PageB*.
On Thu, Sep 8, 2011 at 8:58 AM, Dan Retzlaff <[email protected]> wrote: > Hi Sander. This is probably too late to be useful. I've been out of town. > > You say cross-page communication worked in 1.4, but I think maybe you were > getting lucky. As discussed here, we ran into the "2 versions" problem with > modal windows in 1.4. > > http://apache-wicket.1842946.n4.nabble.com/Data-Sharing-with-InlineFrame-Pages-td3068425.html > > Basically, if PageA modifies something in PageB, PageA needs to have a > reference to PageB itself; a reference to an object in PageA is generally > not sufficient to update the page map entry for PageA. > > Dan > > > On Fri, Aug 26, 2011 at 10:17 AM, Sander Plas <[email protected]> wrote: > >> 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-unsubscribe@wicket.**apache.org<[email protected]> >> For additional commands, e-mail: [email protected] >> >> >
