Ugh! Looks like this was a false alarm.
I went back through again to verify that 2.6 was configured correctly and
to reproduce this again, but this time is worked fine! The only difference
appears to be that I referenced a non-existent Gin 2.1.2 in my WEB-INF/lib
when the issues occurred. Putti
I've been testing my app with GWT 2.6rc4 today. I ran into an issue where I
wasn't being prompted before navigating away from a presenter who returned
non-null in mayStop(). This should be opening a native confirm dialog and
asking the user OK/CANCEL. It works fine in GWT 2.5.1, but in 2.6rc4 it
Generally I just exclude the super classes from the project; since there
should always a server-side equivalent, the rest of the code should still
compile. You lose syntax checking on the super files, though.
On Wed, Jan 15, 2014 at 12:10 PM, Danilo Reinert wrote:
> I'm unable to avoid java com
Hi Liu,
I agree and share your considerations,
but I think it is best to address the issue with a better modularization of
the whole GWT distribution.
In fact it is not just a problem of the gwt-servlet.jar, but it is a
problem also affecting gwt-user.jar and gwt-dev.jar:
all features of GWT in t
We have a number of JavaScriptObject subclasses. As I'm testing out
2.6.0-rc4, I'm getting an NPE from the compiler. (GWT 2.5.1 works without
any issue on our code base.)
I've attached a file with the full error, but here's an excerpt:
Caused by: java.lang.NullPointerException
> at com.google.
any follow up on this?
would like to see a saner gwt-servlet.jar
include a 6M jar just to serve a single RemoteServlet is just absurd ...
On Friday, June 25, 2010 4:09:29 AM UTC+8, Freeland Abbott wrote:
>
> Right now, if you pore through servlet/build.xml, we build gwt-servlet.jar
> by fir
