Re: Type Corruption migrating from GWT 2.6.1 => 2.7.0

On Thursday, July 6, 2017 at 11:59:01 AM UTC+2, bobbit...@gmail.com 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"

Re: Type Corruption migrating from GWT 2.6.1 => 2.7.0

Just a shot in the dark. maybe you changed the linker ? IIRC the default changed around 2.7. Good luck. A. On Thu, Jul 6, 2017 at 11:59 AM wrote: > OK, it looks like we have two "apps" each with its own entry point, but > they share the content of $wnd, which

Re: Type Corruption migrating from GWT 2.6.1 => 2.7.0

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

Re: Type Corruption migrating from GWT 2.6.1 => 2.7.0

It definitely appears to be the case that having multiple GWT window objects (as frames) is playing a role in the problem. The main window has two frames, and some GWT JSNI runs inside each of the two frames. When JSNI in one frame calls the other, the type information on the passed objects

Re: Type Corruption migrating from GWT 2.6.1 => 2.7.0

We have a huge Framework so that may not be an easy task - but I'll see if I can get a standalone case. Within the stack frame I was investigating, I noticed that the window object seemed to change across frames, so perhaps the $entry() arguments were stripped of some of their properties (or

Type Corruption migrating from GWT 2.6.1 => 2.7.0

Could you post a snippet reproducing the issue? -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this

Type Corruption migrating from GWT 2.6.1 => 2.7.0

We're seeing an issue in GWT 2.7.0 where if a Java Object is passed to a JS method that's wrapped with $entry(), then the type information is stripped off. So for example, if a LinkedMap instance is created, and passed through an API wrapped with $entry(), it's typeMarker$ attribute will be