GWT 2.8 - Issue with Javadoc and com.google.web.bindery.event.shared.Event

Hi there, I'm working on transitioning to GWT 2.8 and I'm encountering an odd error that I have not seen in previous GWT versions when generating javadocs for my project: [javadoc] bad source file: C:\dev\depot\lego\module\ui-framework\2.2.0\lib\gwt-user-2.8.0.jar(com/google/web/bindery/ev

Re: GWT and Oracle

Came across this presentation in the context of the recent Java One conference. Seems to be pushing OracleJET more than anything else, ignores GWT (Angular is mentioned), but does reference DukeScript which seems more interesting to me than the other slides presented (similar to GWT/Inbox idea,

Re: System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

Tried out the GWT compile with "optimize 0" and didn't run into the error. Guess it is not an optimization issue... On Friday, August 5, 2016 at 4:36:26 PM UTC-7, Thomas Broyer wrote: > > SDM is meant to be "no optimization" (actually it was originally called > Super Draft Mode). What I was sug

Re: System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

We have static initialization as well, was just trying to illustrate the issue. We ended up just removing the variable... it's actually in some "shared" code so we get funny looks when we ask for oddball syntax changes like this just to make GWT happy. public class MyClass { public static

System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

Hi there, Pretty simple example, but seems like possibly a bug or oddity in GWT 2.8b1 between the command line and the Eclipse plug in. Setup: In a Module.gwt.xml file we define a property like so: In a class we use it like so (paraphrased): public class MyClass { public static final S

Re: 2.8.0 RC1 is here!

> > > FWIW, our project at work still compiles with JDK 7 and GIN 1.5.0; I just > updated GWT to 2.8.0-rc1 and Guava to 20.0-SNAPSHOT (note: I haven't tested > SuperDevMode yet, but I'm rather confident) > If I update to GIN 2.1.2 (which uses its custom classloader), than it > fails with: > [IN

Re: GWT RPC in GWT 3.0+

I was contrasting the blog post to the presentations Ray/Daniel have given in the past, hence the Singular example preceding what you are quoting. These are on youtube and I've also attended their presentations in person. I'm not trying to argue the compilation efficiency of GWT-RPC or get an

Re: GWT RPC in GWT 3.0+

> > > > The compile time argument has me scratching my head. > > I can't find any such argument in Daniel's blog post. > "Slow compiles due to global analysis" section. Specifically talks about the global knowledge vs incremental compile issue. -- You received this message because you are sub

Re: GWT RPC in GWT 3.0+

We've been using GWT-RPC for a while now as well, and the alternatives seemed less desirable the last time I poked around at them. Reading over some of the cited poor choices GWT-RPC, they seem to me to be more like "features" and "trade-offs" instead of simply being bad choices. Version skew

Re: GWT 2.8b1: "runAsyncCallback7 is not a function" - compiler error with GWT.runAsync(...)?

I did add a custom linker in order to get HTTPS sort of working for SDM debugging. A very simple class derived from CrossSiteIframeLinker and only overriding getJsDevModeRedirectHookPermitted(...). No custom linker was used previously. Feels like a regression to me... I guess I'd need to check

Re: GWT 2.8b1: "runAsyncCallback7 is not a function" - compiler error with GWT.runAsync(...)?

I haven't managed to find any further info here... suppose I'll regard GWT.runAsync() as "broken" avoid it going forward. -- 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 ema

Re: Super Dev Mode over HTTPS, workarounds?

Setting up yet another web server sounds quite a bit sub-ideal to me... Thanks for the info though. Sounds like: 1) Open an HTTP port or 2) Force Chrome to accept insecure content Seem to be to most viable solutions at present... here's hoping we get a better solution thru SDM proper in the near

GWT 2.8b1: "runAsyncCallback7 is not a function" - compiler error with GWT.runAsync(...)?

Hi there, I've been migrating an application from GWT 2.5 to GWT2.8b1. After working around how to debug in Super Dev Mode and getting the app to run relatively smoothly, we've encountered an odd issue in the generated JS code which does not show up when debugging: Stack Trace from Chrome: Un

Re: Super Dev Mode over HTTPS, workarounds?

I'm not sure what difference that might make, could you elaborate? I already have one web server talking https to the browser and the SDM script tries to invoke an http connection to the code server. How does adding another server talking HTTPS help the situation? Sorry if I'm not understandin

Super Dev Mode over HTTPS, workarounds?

Greetings! I've been working on migrating our application over to GWT-2.8b1 (from GWT 2.5) and moving from the classic Dev Mode to Super Dev Mode. Migrating a simple sandbox environment went fairly smoothly, and SDM worked just fine for that example, however I have run into problems with using