Thursday, July 6, 2017

Re: Type Corruption migrating from GWT 2.6.1 => 2.7.0

On Thursday, July 6, 2017 at 11:59:01 AM UTC+2, wrote:
OK, it looks like we have two "apps" each with its own entry point, but they share the content of $wnd, which contains a JS Framework.  So the problem is that JS calls can enter either "app" and each "app" appears to be have it's own frame (So $wnd.frames is an array of two windows.)

As mentioned, the problem is that because because both "apps" are plugged into the JS Framework, one might see a GWT object created by the other, but type comparison of objects created in one "app" fails in the other.  This worked in SGWT 2.6.1, but doesn't in GWT 2.7.0.

Does that provide enough detail to answer the question?  Has handling of multiple apps (or "entry points") for a single browser window changed in GWT 2.7.0, specifically with respect to type comparison?

This has never been a supported use-case, there never was any guarantee that it'd work, for as long as I can remember (and I started with GWT 1.4.61; well, actually, I believe at that time having several GWT apps on the same page wasn't even supported).
I believe you can find issues about this if you go far enough in the past (see and which seem related, there probably are others)
I'm even surprised it could have ever worked.
AFAIK, the only situation where this *could* work would be if the two frames/windows load the exact same GWT app code (but execute different code paths in the onModuleLoad based on the URL or some other aspect of the host page).

So while there might have been a change in GWT 2.7 related to how type information of objects is represented, it cannot be called a bug or regression. Sorry.

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment