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

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

How to contact www.gwtproject.org Website?

I looked all over that website, but either there's no contact option or it's hidden very well. How do I send feedback about a problem with the website? I noticed that they provide SHA1 sums for the GWT downloads, but that's strange because Google itself reported that SHA1 is vulnerable

How to determine whether you're in SuperDevMode inside (custom) linker code

Inside the linker code, I can only use com.google.gwt.core.shared.GWT, so I can't call APIs such as GWT.getModuleBaseForStaticFiles() or GWT.getModuleBaseURL() (which people have used to detect SDM) and while GWT.create() is doc'd in com.google.gwt.core.shared.GWT, it doesn't work and throws a

Re: Missing Custom Linker Output Files when using GWT Eclipse Plugin

I guess I didn't ask the right question. What I really want to do is emit a resource from my custom linker that gets written into the "real" war directory that the browser is targeting - so that you don't need an http://localhost:9876/... URL to retrieve it. Is that possible? -- You

Re: Missing Custom Linker Output Files when using GWT Eclipse Plugin

Is my issue the same as Vitaly's in this thread ? So I just "need to use GWT.getModuleBaseForStaticFiles() instead of GWT.getModuleBaseURL()."? I'm

Condition definition of property

I've set up deferred binding to use a different class with SDM, which works fine for GWT 2.6+ However, this causes an error with GWT 2.5.1, because "superdevmode" isn't defined. So I have the following questions: - Is there a clause similar to but that tolerates the

Missing Custom Linker Output Files when using GWT Eclipse Plugin

When using the GWT 2.7 Eclipse Plugin and a custom linker, if I create a new artifact, foo.js, inside the linker, it doesn't show up when I try to load it from the main web page of my application. I need to create this file to dynamically load certain script files. I already observed that the

Bogus warnings from GWT-2.8 Beta

If we define a class Foo in GWT with a JSNI method: private native void logStuff() /*-{ $wnd.myLog("This object has class" + th...@java.lang.Object::getClass()()); }-*/; then we getting a spurious warning: [WARN] JSNI method Foo.logStuff()V calls method >

Re: Download link for GWT 2.8 SNAPSHOT SDK?

I'm using GWT via ant on the command-line, not Eclipse. I guess building it from the GitHub source is the simplest route. On Thursday, August 6, 2015 at 1:32:05 PM UTC-5, Jens wrote: GWT only publishes SNAPSHOT Maven artifacts. If you want a full SDK then you have to build it yourself.

Download link for GWT 2.8 SNAPSHOT SDK?

My Google-Fu must be weak, but I can't seem to find a download link for GWT 2.8 SNAPSHOT (I know this is a pre release build). So the file I'm looking for will likely be named gwt-2.8.0-SNAPSHOT.zip. I was able to find the released SDKs, the GWT GitHub Repository, and some links to

Problems Remote Debugging with SourceMaps in SuperDevMode

Using Chrome, I've got SDM working locally - reloading the page trips the CodeServer I have running in Eclipse, and the sourcemaps are accessible in Chrome via 127.0.0.1:9876 in the sources tab. However, I wanted to try access from another machine. So I made the changes to my setup that are

Re: Problems Remote Debugging with SourceMaps in SuperDevMode

Looking over on GitHub for existing issues, I saw that someone else reported an issue with DNS resolution. With that in mind, I modified by client machine's host file to include a binding for the fully qualified name of my host machine, and when I reloaded hte page, source maps were there!

[gwt-contrib] Re: GWT 2.7.0 Custom Linker Problem - module.nocache.js Artifact content mismatches file

On Wednesday, June 24, 2015 at 3:42:47 PM UTC-5, Jens wrote: - Why are the post-linkers fed misleading content for the module.nocache.js file Artifact that doesn't represent what will be the file system content of that file? A production compile and SuperDevMode work different

[gwt-contrib] GWT 2.7.0 Custom Linker Problem - module.nocache.js Artifact content mismatches file

To solve an issue with our particular use of GWT, we implement our own post Linker for GWT. This post linker appends a block of JS code to the end of module.nocache.js, by detecting the nocache.js file when it's passed to the link() command in the ArtifactSet, and replacing it with a new

Re: How to rescue Classic Dev Mode?

The GWT team might want to survey existing users of their product before breaking backcompat. A normal company wants to keep customers happy, and provide updates that don't break existing code bases. However, I suppose a company with a huge market share and endless resources can act with

Re: How to rescue Classic Dev Mode?

On Sunday, June 21, 2015 at 3:20:51 PM UTC-5, Thomas Broyer wrote: On Sunday, June 21, 2015 at 9:35:35 PM UTC+2, Lukas Glowania wrote: Which announcements in particular would make it to a dead end? The new compiler, JSNI (removed) vs. JsInterop (doesn't work in DevMode). That would

Re: How to rescue Classic Dev Mode?

On Monday, June 22, 2015 at 6:19:27 AM UTC-5, Jens wrote: Say WHAT!? JSNI is going to be removed!? They realize that's going to break a bunch of existing code, right? It only breaks if you upgrade to GWT 3.0 and GWT 3.0 is expected to be a very breaking upgrade. So a lot of code will

GWT 2.7.0 Custom Linker Problem - module.nocache.js Artifact content mismatches file

To solve an issue with our particular use of GWT, we implement our own post Linker for GWT. This post linker appends a block of JS code to the end of module.nocache.js, by detecting the nocache.js file when it's passed to the link() command in the ArtifactSet, and replacing it with a new

Avoiding Copying Public Artifacts during every Incremental Recompile in SuperDevMode

If you have a GWT Module with public artifacts specified, then for every Java tweak, the incremental recompile in SDM will recopy ALL of the public artifacts (typically from a JAR to an output directory). This seems to run after the last linker: Invoking Linker RPC log linker Invoking

Module Inheritance and path excludes

Suppose we define a GWT Module *ImageResources* that includes certain resources in its default public directory, and then we define a Module *Excluder* that specifically excludes those resources via something like: module public path=imageResources/public excludes=**/*/ /module Then we can

Re: Module Inheritance and path excludes

Just as the excludes seems to be too powerful and exclude the files *everywhere*, regardless of the inheritance topology, the skips seems to be* too weak*. In my tests, if I convert the *Excluder* Module to use skips, it appears to do *nothing* when included by Module *B* as I described above

Calling getVersion() to get the GWT version from a Linker

I'd like to get the GWT version from inside a linker (say the link() method) which in client code can be done via GWT.getVersionI(), however, nothing I've tried appears to work. You can't use the client version of GWT as that leads to a runtime Java exception since the method getVersion()

Finding out what Primary Linker is Active, inside a Post Linker

I'm trying to solve a problem. I've written a custom post (non-primary) linker extending AbstractLinker, but I want it to have different behavior depending on what the primary linker is. For example, the primary linker could be the standard linker or the xsiframe linker. I could attempt to

Re: Finding out what Primary Linker is Active, inside a Post Linker

Maybe I'm missing something, but looking at the code briefly, I see that StandardLinkerContext()'s constructor takes the ModuleDef, and the ModuleDef is passed around throughout the linking process, so I'm guessing a strong reference to the ModuleDef would persist throughout the linking