Google Web Toolkit: January 2018

Wednesday, January 31, 2018

Announcement: availability of gwt-jackson-objectify extension

For those using Objectify and GWT (and more precisely objectify-gwt: use your Objectify data models directly in your client-side via GWT RPC).

If you wanna migrate to a Rest/JSON API, it's now possible by using resty-gwt (that use gwt-jackson and the new gwt-jackson-objectify extension)

And here a little demo project: https://github.com/freddyboucher/gwt-storage-objectify (live demo: https://gwt-storage-objectify.appspot.com/)

Cheers.

Freddy.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Superdev doesn't work with GWT 2.8.2 & IntelliJ 14

Also note, We were using GWT 2.6.1 before and DEV mode on IJ was working fine. We upgraded to GWT 2.8.2 and DEV mode is deprecated and trying to use Super Dev mode and it's not working.

On Wednesday, January 31, 2018 at 1:22:05 PM UTC-6, BM wrote:

Hi Jens,
Thanks for the reply. Yes we use maven and added following dependencies. We also use gwtbootstrap3 and GWTP.

<properties>

<gwtVersion>2.8.2</gwtVersion>
</properties>

<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-servlet</artifactId>
<version>${gwtVersion}</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>${gwtVersion}</version>
<scope>provided</scope>
</dependency>
</dependency>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>${gwtVersion}</version>
</plugin>

So which dependencies for colt I would need to add in my pom file? Sorry I am bit lost here.

On Tuesday, January 30, 2018 at 2:08:25 PM UTC-6, Jens wrote:
If you have downloaded GWT 2.8.2 from Maven, then the "colt" library (and lots of other libs) is not bundled into gwt-dev.jar. If your project does not use Maven then you need to add these libraries manually to your class path.

See:
http://search.maven.org/remotecontent?filepath=com/google/gwt/gwt/2.8.2/gwt-2.8.2.pom
http://search.maven.org/remotecontent?filepath=com/google/gwt/gwt-dev/2.8.2/gwt-dev-2.8.2.pom

Alternatively download GWT 2.8.2 from gwtproject.org, then all theses dependencies are bundled into gwt-dev.jar and things should just work as usual.

-- J.

Re: Superdev doesn't work with GWT 2.8.2 & IntelliJ 14

Hi Jens,

Thanks for the reply. Yes we use maven and added following dependencies. We also use gwtbootstrap3 and GWTP.

</properties>

<groupId>com.google.gwt</groupId>

<artifactId>gwt-servlet</artifactId>

<version>${gwtVersion}</version>

<scope>runtime</scope>

</dependency>

<groupId>com.google.gwt</groupId>

<version>${gwtVersion}</version>

<scope>provided</scope>

</dependency>

<groupId>org.codehaus.mojo</groupId>

<artifactId>gwt-maven-plugin</artifactId>

<version>${gwtVersion}</version>

</plugin>

So which dependencies for colt I would need to add in my pom file? Sorry I am bit lost here.

On Tuesday, January 30, 2018 at 2:08:25 PM UTC-6, Jens wrote:

If you have downloaded GWT 2.8.2 from Maven, then the "colt" library (and lots of other libs) is not bundled into gwt-dev.jar. If your project does not use Maven then you need to add these libraries manually to your class path.

See:
http://search.maven.org/remotecontent?filepath=com/google/gwt/gwt/2.8.2/gwt-2.8.2.pom
http://search.maven.org/remotecontent?filepath=com/google/gwt/gwt-dev/2.8.2/gwt-dev-2.8.2.pom

Alternatively download GWT 2.8.2 from gwtproject.org, then all theses dependencies are bundled into gwt-dev.jar and things should just work as usual.

-- J.

Re: GWT 2.8.2 release

Hello Thomas,

thank you very much for your help. I'm sorry for replying so late. I could not work on the problem all the time.

I think using the compiler-plugin 3.6 and the artifact "gwt" as an import-scope-dependency were the most important advices. Before that, we had direct dependencies to gwt-user, gwt-dev and gwt-servlet, which led to those messy transitive dependencies.

One more thing, that I want to share:

During the update I had some strange error messages, that pointed me into the wrong direction:

[INFO] auto discovered modules [Entrypoint]
[INFO] Compiling module Entrypoint
[INFO] Computing all possible rebind results for 'Injector'
[INFO] Rebinding Injector
[INFO] Invoking generator com.google.gwt.inject.rebind.GinjectorGenerator
[INFO] Resolving bindings for Injector
[INFO] [ERROR] Exception while visiting Key[type=myClass, annotation=[none]]
[INFO] [ERROR] Generator 'com.google.gwt.inject.rebind.GinjectorGenerator' threw an exception while rebinding 'Injector'
[INFO] java.lang.SecurityException: Prohibited package name: java.lang

In fact it was a

try {

}

catch (JavaScriptException e) {

}

that was the problem. When I replaced JavaScriptException with the more general "Exception" everything was fine. And the error only occured during the compilation of the GIN dependency management.

Without GIN everything was fine. Really strange.

I also had problems with self defined annotations, but that were all problems that I could manage for myself.

Thank you again for your help.

Jörg Pfründer

2018-01-16 11:08 GMT+01:00 Thomas Broyer <t.broyer@gmail.com>:

On Tuesday, January 16, 2018 at 10:47:51 AM UTC+1, Jörg Pfründer wrote:
Dear GWT-Team,

thank you that you have done a great job in the past. We have a large codebase strongly relying on GWT. However the last release has caused big pain to me:

I have tried to update from version 2.7 to 2.8.2 to get rid of my dirty bugfix hacks for chrome 61 positioning.

But I was not able to upgrade my codebase due to very many problems with dependencies in the current gwt 2.8.2 release.
BTW: I use maven to build our project:

1) gwt-dev has dependencies to different jetty versions and as far as I know, I need gwt-dev for the development mode:

Dependency convergence error for org.eclipse.jetty:jetty-io:9.2.13.v20150730 paths to dependency are:
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-net.sourceforge.htmlunit:htmlunit:2.19
      +-org.eclipse.jetty.websocket:websocket-client:9.2.13.v20150730
        +-org.eclipse.jetty:jetty-io:9.2.13.v20150730
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-net.sourceforge.htmlunit:htmlunit:2.19
      +-org.eclipse.jetty.websocket:websocket-client:9.2.13.v20150730
        +-org.eclipse.jetty.websocket:websocket-common:9.2.13.v20150730
          +-org.eclipse.jetty:jetty-io:9.2.13.v20150730
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-org.eclipse.jetty:jetty-webapp:9.2.14.v20151106
      +-org.eclipse.jetty:jetty-servlet:9.2.14.v20151106
        +-org.eclipse.jetty:jetty-security:9.2.14.v20151106
          +-org.eclipse.jetty:jetty-server:9.2.14.v20151106
            +-org.eclipse.jetty:jetty-io:9.2.14.v20151106
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-org.eclipse.jetty:jetty-servlets:9.2.14.v20151106
      +-org.eclipse.jetty:jetty-io:9.2.14.v20151106

Dependency convergence error for org.eclipse.jetty:jetty-util:9.2.13.v20150730 paths to dependency are:
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-net.sourceforge.htmlunit:htmlunit:2.19
      +-org.eclipse.jetty.websocket:websocket-client:9.2.13.v20150730
        +-org.eclipse.jetty:jetty-util:9.2.13.v20150730
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-net.sourceforge.htmlunit:htmlunit:2.19
      +-org.eclipse.jetty.websocket:websocket-client:9.2.13.v20150730
        +-org.eclipse.jetty.websocket:websocket-common:9.2.13.v20150730
          +-org.eclipse.jetty:jetty-util:9.2.13.v20150730
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-org.eclipse.jetty:jetty-webapp:9.2.14.v20151106
      +-org.eclipse.jetty:jetty-xml:9.2.14.v20151106
        +-org.eclipse.jetty:jetty-util:9.2.14.v20151106
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-org.eclipse.jetty:jetty-servlets:9.2.14.v20151106
      +-org.eclipse.jetty:jetty-http:9.2.14.v20151106
        +-org.eclipse.jetty:jetty-util:9.2.14.v20151106
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-org.eclipse.jetty:jetty-servlets:9.2.14.v20151106
      +-org.eclipse.jetty:jetty-util:9.2.14.v20151106
and
+-myproject
+-com.google.gwt:gwt-dev:2.8.2
    +-org.eclipse.jetty:jetty-annotations:9.2.14.v20151106
      +-org.eclipse.jetty:jetty-plus:9.2.14.v20151106
        +-org.eclipse.jetty:jetty-jndi:9.2.14.v20151106
          +-org.eclipse.jetty:jetty-util:9.2.14.v20151106

We do not allow dependencies to different versions of the same library, since it is not possible to have to versions of the same library in the classpath.
So I tried to fix the jetty dependencies to version 9.2.14.v20151106 which is really sort of ugly.

Did you use the com.google.gwt:gwt with scope=import in dependency management? This should declare all Jetty dependencies (not all of them, but all those directly depended on, just not the ones that only Jetty itself has dependencies on) and might be enough to fix your problem.

<dependencyManagement> <dependencies> <dependency> <groupId>com.google.gwt</groupId> <artifactId>gwt</artifactId> <version>2.8.2</version> <type>pom</type> <scope>import</scope> </dependency> …

2) Then I tried to build the project.

It said:

Execution default-compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile failed: A required class was missing while executing org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile: javax/lang/model/element/ModuleElement
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.apache.maven.plugins:maven-compiler-plugin:3.7.0
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/joerg/ideaprojects/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/3.7.0/maven-compiler-plugin-3.7.0.jar
[ERROR] urls[1] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/groovy/groovy-eclipse-compiler/2.9.2-03/groovy-eclipse-compiler-2.9.2-03.jar
[ERROR] urls[2] = file:/home/joerg/ideaprojects/.m2/repository/org/apache/xbean/xbean-reflect/3.7/xbean-reflect-3.7.jar
[ERROR] urls[3] = file:/home/joerg/ideaprojects/.m2/repository/com/google/collections/google-collections/1.0/google-collections-1.0.jar
[ERROR] urls[4] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/groovy/groovy-eclipse-batch/2.4.13-01/groovy-eclipse-batch-2.4.13-01.jar
[ERROR] urls[5] = file:/home/joerg/ideaprojects/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[6] = file:/home/joerg/ideaprojects/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[7] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[8] = file:/home/joerg/ideaprojects/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[9] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[10] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.6/plexus-component-annotations-1.6.jar
[ERROR] urls[11] = file:/home/joerg/ideaprojects/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[12] = file:/home/joerg/ideaprojects/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[13] = file:/home/joerg/ideaprojects/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
[ERROR] urls[14] = file:/home/joerg/ideaprojects/.m2/repository/commons-io/commons-io/2.5/commons-io-2.5.jar
[ERROR] urls[15] = file:/home/joerg/ideaprojects/.m2/repository/org/apache/maven/shared/maven-shared-incremental/1.1/maven-shared-incremental-1.1.jar
[ERROR] urls[16] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/plexus/plexus-java/0.9.2/plexus-java-0.9.2.jar
[ERROR] urls[17] = file:/home/joerg/ideaprojects/.m2/repository/org/ow2/asm/asm/6.0_BETA/asm-6.0_BETA.jar
[ERROR] urls[18] = file:/home/joerg/ideaprojects/.m2/repository/com/thoughtworks/qdox/qdox/2.0-M7/qdox-2.0-M7.jar
[ERROR] urls[19] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/plexus/plexus-compiler-api/2.8.2/plexus-compiler-api-2.8.2.jar
[ERROR] urls[20] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/plexus/plexus-compiler-manager/2.8.2/plexus-compiler-manager-2.8.2.jar
[ERROR] urls[21] = file:/home/joerg/ideaprojects/.m2/repository/org/codehaus/plexus/plexus-compiler-javac/2.8.2/plexus-compiler-javac-2.8.2.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR] : javax.lang.model.element.ModuleElement
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command

"javax/lang/model/element/ModuleElement" ??
Then I realized that you had said "GWT can now run on Java 9" in the release notes. You did not say: "GWT-Compiler must now run on Java 9"...

Nether the less I tried to set my JAVA_HOME to jdk 9 and error disappeared. (It caused many other problems to switch to Java 9 but that's a different story).

This is the maven-compiler-plugin, not GWT. Maybe try using version 3.6 rather than 3.7 if you're not using Java 9?

3) But Jetty 9.4.7 is the first jetty-project with basic java 9 support. So I had to upgrade my jetty-version.
4) Now I had to patch org.eclipse.jetty.server.Request because GWT calls a method getUri which has been renamed to getHttpURI() .
5) Then I had to patch org.eclipse.jetty.webapp.WebAppClassLoader because we have several dependencies probing for the existence of classes by trying to instancate them via reflection, which caused NullPointerExceptions in the Java 9 classloader. I had to catch them in the WebbAppClassLoader and convert them into ClassNotFoundExceptions.

The first GWT-Project has been built successfully and could be run in development mode. I thought: I'm done!

6) But then next project used GIN-Injection. And GIN does not build with Java9 due to SecurityException:

[INFO]             [ERROR] Generator 'com.google.gwt.inject.rebind.GinjectorGenerator' threw an exception while rebinding 'myInjector'
[INFO] java.lang.SecurityException: Prohibited package name: java.lang
[INFO]     at java.base/java.lang.ClassLoader.preDefineClass(ClassLoader.java:889)
[INFO]     at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1005)
[INFO]     at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:868)
[INFO]     at com.google.gwt.inject.rebind.GinBridgeClassLoader.findClass(GinBridgeClassLoader.java:160)
[INFO]     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:563)
[INFO]     at com.google.gwt.inject.rebind.GinBridgeClassLoader.loadClass(GinBridgeClassLoader.java:103)
[INFO]     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
[INFO]     at java.base/java.lang.ClassLoader.defineClass1(Native Method)
[INFO]     at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
[INFO]     at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:868)
[INFO]     at com.google.gwt.inject.rebind.GinBridgeClassLoader.findClass(GinBridgeClassLoader.java:160)
[INFO]     at com.google.gwt.inject.rebind.GinBridgeClassLoader.loadClass(GinBridgeClassLoader.java:106)
[INFO]     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
[INFO]     at java.base/java.lang.ClassLoader.defineClass1(Native Method)
[INFO]     at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
[INFO]     at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:868)
[INFO]     at com.google.gwt.inject.rebind.GinBridgeClassLoader.findClass(GinBridgeClassLoader.java:160)
[INFO]     at com.google.gwt.inject.rebind.GinBridgeClassLoader.loadClass(GinBridgeClassLoader.java:106)
[INFO]     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
[INFO]     at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
[INFO]     at java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3110)
[INFO]     at java.base/java.lang.Class.getDeclaredConstructors(Class.java:2314)
[INFO]     at com.google.gwt.inject.rebind.resolution.ImplicitBindingCreator.getInjectConstructor(ImplicitBindingCreator.java:270)
[INFO]     at com.google.gwt.inject.rebind.resolution.ImplicitBindingCreator.createImplicitBindingForClass(ImplicitBindingCreator.java:146)
[INFO]     at com.google.gwt.inject.rebind.resolution.ImplicitBindingCreator.create(ImplicitBindingCreator.java:140)
[INFO]     at com.google.gwt.inject.rebind.resolution.DependencyExplorer.visit(DependencyExplorer.java:106)
[INFO]     at com.google.gwt.inject.rebind.resolution.DependencyExplorer.explore(DependencyExplorer.java:89)
[INFO]     at com.google.gwt.inject.rebind.resolution.BindingResolver.resolveBindings(BindingResolver.java:70)
[INFO]     at com.google.gwt.inject.rebind.GinjectorBindings.resolveBindings(GinjectorBindings.java:238)
[INFO]     at com.google.gwt.inject.rebind.BindingsProcessor.resolveAllUnresolvedBindings(BindingsProcessor.java:146)
[INFO]     at com.google.gwt.inject.rebind.BindingsProcessor.process(BindingsProcessor.java:105)
[INFO]     at com.google.gwt.inject.rebind.GinjectorGeneratorImpl.generate(GinjectorGeneratorImpl.java:79)
[INFO]     at com.google.gwt.inject.rebind.GinjectorGenerator.generate(GinjectorGenerator.java:74)
[INFO]     at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(IncrementalGenerator.java:40)
[INFO]     at com.google.gwt.dev.javac.StandardGeneratorContext.runGeneratorIncrementally(StandardGeneratorContext.java:745)
[INFO]     at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:103)
[INFO]     at com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(StandardRebindOracle.java:78)
[INFO]     at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:262)
[INFO]     at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:251)
[INFO]     at com.google.gwt.dev.PrecompilationContextCreator$1.getAllPossibleRebindAnswers(PrecompilationContextCreator.java:86)
[INFO]     at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createStaticRebindExpression(UnifyAst.java:519)
[INFO]     at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createRebindExpression(UnifyAst.java:487)
[INFO]     at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.maybeHandleMagicMethodCall(UnifyAst.java:415)
[INFO]     at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.visit(UnifyAst.java:402)
[INFO]     at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:265)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
[INFO]     at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
[INFO]     at com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:76)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
[INFO]     at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
[INFO]     at com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:88)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:331)
[INFO]     at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:94)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
[INFO]     at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:139)
[INFO]     at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:135)
[INFO]     at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
[INFO]     at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:786)
[INFO]     at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:778)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
[INFO]     at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
[INFO]     at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1401)
[INFO]     at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:896)
[INFO]     at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1410)
[INFO]     at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1222)
[INFO]     at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:1140)
[INFO]     at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:255)
[INFO]     at com.google.gwt.dev.Precompile.precompile(Precompile.java:255)
[INFO]     at com.google.gwt.dev.Precompile.precompile(Precompile.java:202)
[INFO]     at com.google.gwt.dev.Precompile.precompile(Precompile.java:143)
[INFO]     at com.google.gwt.dev.Compiler.compile(Compiler.java:204)
[INFO]     at com.google.gwt.dev.Compiler.compile(Compiler.java:155)
[INFO]     at com.google.gwt.dev.Compiler.compile(Compiler.java:144)
[INFO]     at com.google.gwt.dev.Compiler$1.run(Compiler.java:118)
[INFO]     at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
[INFO]     at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
[INFO]     at com.google.gwt.dev.Compiler.main(Compiler.java:125)

I'm really upset after several days of work for nothing.

So:
Please publish a release with a bugfix for Chrome 61, that does not force me to upgrade my build to java9!

I don't use Java 9; GWT does not force you to use Java 9 (quite the contrary actually).

Please fix your jetty-dependencies!

GWT itself depends on 9.2.14, HtmlUnit depends on 9.2.13; but our BOM (com.google.gwt:gwt) should declare all required Jetty versions. Could you try and tell us if it needs updating?
(btw, you opted into using dependency convergence enforcement rules, which is a PITA by itself; without it, all Jetty dependencies from gwt-dev and gwt-user should be resolved to 9.2.14, so there's no problem here)

Please do not mix bugfix releases (Chrome 61) and new feature releases (Java 9) in the future!

Kind regards

Jörg Pfründer

Am Donnerstag, 19. Oktober 2017 22:30:49 UTC+2 schrieb Colin Alworth:
Today we released the next version of GWT, version 2.8.2. A few quick highlights from this new release:
GWT can now run on Java 9 (though Java 9 features are not yet supported, coming soon!)
Chrome 61 change in getAbsoluteTop/Left has been fixed
Errors on the page reported from window.onerror are now reported to your uncaught exception handler
GWT now generates CSP compliant dom elements
The release notes can be found at http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_2. Get yours from Maven Central, or from the zip release.

Special thanks to Max Barkley of RedHat who helped lead the release effort this time, and to all of the fantastic testers who helped us ensure that this release was ready to go.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/xuwG4Uewt8M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--------------------------
Bitte meine E-Mailadresse nicht an Dritte weitergeben.
Bitte keine E-Mails an mich mit großem CC-Verteiler schicken.
Geben Sie meine E-Mailadresse nicht an Facebook weiter.
Wenn Sie Facebook benutzen, löschen Sie meine E-Mails sofort nach Erhalt aus Ihrem Postfach oder Sie verzichten auf die Freunde-finden-Funktion.

Tuesday, January 30, 2018

Re: Serialization /Incompatible/ classnot found

Hello, it might be related to this. I created issue https://github.com/gwtproject/gwt/issues/9593
Check whether your hash map contains arrays of objects.

Re: Superdev doesn't work with GWT 2.8.2 & IntelliJ 14

If you have downloaded GWT 2.8.2 from Maven, then the "colt" library (and lots of other libs) is not bundled into gwt-dev.jar. If your project does not use Maven then you need to add these libraries manually to your class path.

See:

http://search.maven.org/remotecontent?filepath=com/google/gwt/gwt/2.8.2/gwt-2.8.2.pom

http://search.maven.org/remotecontent?filepath=com/google/gwt/gwt-dev/2.8.2/gwt-dev-2.8.2.pom

Alternatively download GWT 2.8.2 from gwtproject.org, then all theses dependencies are bundled into gwt-dev.jar and things should just work as usual.

-- J.

Re: Take advantage of the JavaScript compilation cache (Chromium)

That Chrome caching is entirely transparent to JavaScript. So you would need to ask the Electron guys if that can be enabled in V8 used by Electron.

If your initial load is 29 MB then I would say split points need to be optimized. Sure GWT's left over fragment grows and grows the more GWT SDK stuff is shared between split points, but at least your own code can probably be split up better. Have you already taken a look at the compile report of GWT (passing -compileReport and -extra <path> to GWT compiler)? I am pretty sure you can spot places that can be optimized.

Also 29 MB seems pretty huge for a single "safari" permutation. Do you really have that much code or do you inline lots of Resources (images, js libs, whatever) into the JS using ClientBundle? I think the compile report also shows some numbers for this.

-- J.

Take advantage of the JavaScript compilation cache (Chromium)

Hi,
our company maintains a GWT application where the development was started 4 years ago and where several dozens of developers has worked on it.

The current version of GWT used is 2.5.1 and the application will be accessible only through the Chromium browser embedded in an ad-hoc client built by using Electron.

Altough we use the GWT code splitting feature, our application suffers of a performance issue because the GWT initial load is 29MB and the user login process spends most time to parse/compile the GWT initial load.

We noted that the V8 JavaScript engine used by Chromium supports a JavaScript code caching mechanism in order to mitigate that kinds of performance issue that we suffer.

So is it possible for a GWT application to take advantage of the V8 JavaScript code cache?

From our tests, we noted that the GWT initial load (embedded in thousands of <script> tags of the XXXXXXXX.cache.html file) is always compiled, even after login/logout operation executed sequentially without closing the browser.

Regards,
Diego

Re: Eclipse (neon) with the GWT app translates the Java code of Paul Falstad's electronic simulator into JavaScript

Thanks. I'll look into it.

On Tuesday, January 30, 2018 at 6:11:43 AM UTC-8, Jens wrote:

First try upgrading to GWT 2.8.2 and check if the problem still exists. If it still exists try compiling the app using -draftCompile which disables nearly all optimizations done by the GWT compiler. If the problem disappears the compiler has done a problematic optimization, which is probably pretty tough to figure out.

-- J.

Superdev doesn't work with GWT 2.8.2 & IntelliJ 14

When I start the debug mode I get following error in the IJ.

Exception in thread "main" java.lang.NoClassDefFoundError: cern/colt/map/OpenIntObjectHashMap

at com.google.gwt.dev.util.collect.IntMultimap.<init>(IntMultimap.java:28)

at com.google.gwt.dev.StringAnalyzableTypeEnvironment.<init>(StringAnalyzableTypeEnvironment.java:68)

at com.google.gwt.dev.MinimalRebuildCache.<init>(MinimalRebuildCache.java:192)

at com.google.gwt.dev.CompilerContext$Builder.<init>(CompilerContext.java:37)

at com.google.gwt.dev.DevModeBase.<init>(DevModeBase.java:636)

at com.google.gwt.dev.DevMode.<init>(DevMode.java:463)

at com.google.gwt.dev.DevMode.main(DevMode.java:430)

Caused by: java.lang.ClassNotFoundException: cern.colt.map.OpenIntObjectHashMap

at java.net.URLClassLoader.findClass(URLClassLoader.java:381)

at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)

at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

... 7 more

Disconnected from the target VM, address: '127.0.0.1:53044', transport: 'socket'

Process finished with exit code 1

Please advise.

Re: Eclipse (neon) with the GWT app translates the Java code of Paul Falstad's electronic simulator into JavaScript

First try upgrading to GWT 2.8.2 and check if the problem still exists. If it still exists try compiling the app using -draftCompile which disables nearly all optimizations done by the GWT compiler. If the problem disappears the compiler has done a problematic optimization, which is probably pretty tough to figure out.

-- J.

Eclipse (neon) with the GWT app translates the Java code of Paul Falstad's electronic simulator into JavaScript

$ 1 0.000039999999999999996 11.086722712598126 50 5 42
T 144 224 224 240 2 100 1 0 0 0.999
c 368 176 400 176 2 1e-11 0
c 352 272 384 272 2 1e-11 0
l 496 336 416 336 2 10000 0
l 240 112 304 112 2 10000 0
w 464 192 432 192 0
w 432 160 496 160 0
w 288 336 288 256 0
w 288 256 320 256 0
w 464 192 464 112 0
w 240 160 240 112 0
w 272 288 320 288 0
w 496 336 496 288 0
r 384 112 464 112 0 470000
160 272 176 240 176 0 4.500000000000001e-9 10000000
w 256 240 256 192 0
160 400 176 432 176 0 4.500000000000001e-9 10000000
160 352 272 320 272 0 4.500000000000001e-9 10000000
160 464 272 496 272 0 4.500000000000001e-9 10000000
w 224 320 272 320 0
w 256 240 480 240 0
w 480 240 480 256 0
w 256 240 256 304 0
w 256 304 336 304 0
w 336 304 336 288 0
w 480 240 480 128 0
w 480 128 416 128 0
w 416 128 416 160 0
x 154 358 293 361 4 15 http://is.gd/infinitegain
x 269 223 464 226 4 13 circuit-20180130-0100.circuitjs.txt
x 155 318 212 321 4 18 Vinyasi
x 344 310 439 313 4 13 AIR-CORE\sCOIL
w 496 256 528 256 0
w 528 256 528 368 0
w 528 368 144 368 0
w 144 368 144 256 0
w 496 160 496 48 0
w 496 48 144 48 0
x 299 79 409 82 4 15 AIR-CORE\sCOIL
w 272 128 208 128 0
w 144 160 144 48 0
A 192 160 192 192 0 1 40 5 0 0 0.5
r 288 336 352 336 0 470000
r 144 160 144 224 0 22000
r 224 256 224 320 0 22000
x 153 271 210 274 4 11 100H\s@\s1:1
187 320 176 368 176 0 3000 1000000 65 0.003
187 384 272 416 272 0 3000 1000000 65 0.003
r 320 176 272 176 0 180
r 416 272 464 272 0 180
w 416 128 272 128 0
w 224 192 240 192 0
c 144 160 192 160 2 5.599999999999999e-7 0
R 208 128 208 80 0 2 80 3 0 0 0.6
w 224 192 224 224 0
w 272 320 272 288 0
r 304 112 384 112 0 2000000
r 352 336 416 336 0 2000000
x 138 425 491 428 4 15 EVERY\s12.5\sMILLI\sSECONDS\sCLIMBING\sTO\sINFINITY.
x 139 401 527 404 4 15 THIS\sIS\sA\sNON-TRAPEZOIDAL\sSIMULATION\sWITH\sSPIKES
b 213 181 211 159 0
x 197 174 209 177 4 24 ↕
x 144 468 156 471 4 24 ↕
b 162 474 160 452 0
x 197 452 526 455 4 14 FLOATING\sCAPACITOR\sPLATE\sWITH\sAIR\sFLOWING
x 195 474 531 477 4 14 BETWEEN\sIT\sAND\sTHE\sANTENNA\sPLATE.\sBOTH\sTHE
x 199 496 526 499 4 14 ANTENNA\sAND\sFLOATING\sPLATE\sARE\sINSULATED.
b 141 474 139 452 0
x 129 490 149 493 4 13 Ant
x 218 174 235 177 4 13 FP
x 167 468 184 471 4 13 FP
x 146 546 540 549 4 12 THIS\sPREVENTS\sLOCAL\sRADIO\sINTERFERENCE\sAND\sAN\sANGRY\sFCC.
x 173 521 538 524 4 11 FLOATING\sPLATE\sIS\sCONNECTED\sTO\sEV\sCHASSIS\sFOR\sCOMMON\sGROUND.
o 4 64 0 4163 4.999999999999999e-16 1e-17 0 2 4 3
o 4 64 0 4353 5 0.1 1 2 4 3
o 3 64 0 4353 5 0.1 2 2 3 3
o 4 64 0 4354 5 0.1 3 2 4 3
o 3 64 0 4354 5 0.1 4 2 3 3
o 41 64 0 4353 5 0.1 5 2 41 3
o 41 64 0 4354 5 0.1 6 1
$ 1 1e-11 5.934295036739208 18 5 42
l 272 16 272 -32 2 1 0
r 272 64 272 16 0 20
c 224 112 160 112 2 1000 0
187 160 112 160 64 0 3000 1000000 65 0.003
c 160 0 160 32 2 0.000009999999999999999 1e-15
r 160 32 160 64 0 0.000001
c 384 0 384 32 2 0.000009999999999999999 1e-15
187 384 112 384 64 0 3000 1000000 65 0.003
c 384 112 320 112 2 1000 0
r 384 32 384 64 0 0.000001
r 272 112 224 112 0 0.000001
r 320 112 272 112 0 0.000001
c 384 -32 272 -32 2 1000 0
c 272 -32 160 -32 2 1000 0
r 160 -32 160 0 0 0.000001
r 384 -32 384 0 0 0.000001
187 272 112 272 64 0 3000 1000000 65 0.003
x -106 20 131 23 4 12 This\scapacitor\sis\sprecharged\swith\s1\spV.\s\s\s--->
x 443 21 676 24 4 12 <--\s\s\sThis\scapacitor\sis\sprecharged\swith\s1\spV.
x -83 48 100 51 4 12 circuit-20170918-1033.circuitjs.txt
x 503 41 614 44 4 12 http://is.gd/capboom
o 0 64 0 4355 5 0.1 0 2 0 3

Paul Falstad makes available to developers his Java source code for his electronic simulator...
https://github.com/pfalstad/circuitjs1

Using the Eclipse (Neon) platform coupled with the GWT app from Google to translate Paul's source code into JavaScript has produced a strange anomaly.

If I run the exact same circuit in his original Java version...
http://www.falstad.com/circuit-java/

...I get very different results, sometimes, then if I run the same circuit in his JavaScript version...
http://www.falstad.com/circuit/

The difference is phenomenal. Infinite gain on some circuits is possible - some so suddenly, that it can be very surprising...
http://vinyasi.info/ne?startCircuit=capboom.txt

He never wrote his simulator with JavaScript in mind. Nor does he participate in its translation from its originally coded version in Java. Yet, electronics theory gets turned on its head whenever I spend countless hours developing my own circuits that defy conventional wisdom!

For example...
http://vinyasi.info/ne?startCircuit=infinite-gain.txt

Anyone have any idea what might be occurring?

Thanks.

Sunday, January 28, 2018

Re: What is Wrong With GWT Widgets

See https://github.com/GwtMaterialDesign/gwt-material/issues/448

Regards,

Rodolfo

On Sun, Jan 28, 2018 at 6:31 AM Alexander Koch <josef.koch@gmail.com> wrote:

Has anyone information on what this could mean for the GWT material project?

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: What is Wrong With GWT Widgets

Has anyone information on what this could mean for the GWT material project?

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Thursday, January 25, 2018

Re: What is Wrong With GWT Widgets

Thank you Thomas for the detailed reply, I hope we see GWT 3.0 soon.

On Tuesday, January 23, 2018 at 7:23:22 PM UTC+2, Thomas Broyer wrote:

On Monday, January 22, 2018 at 11:09:27 PM UTC+1, Mutaz Alghafary wrote:
What is exactly the problem with GWT Widgets, I am new to GWT and I have been watching some sessions about the future of GWT , it seems everyone agrees that you should not be using GWT Widgets, and use things like Elemental or other UI libraries ?

Nothing "wrong" with them, besides : they're a lot of code to maintain, sometimes quite complex, Google won't maintain them anymore, so it's big work left to the community. That doesn't mean they'll necessarily be deprecated, etc. but maintaining them has a cost.
Other reasons are: they rely on com.google.gwt.dom which makes extensive use of JSNI (and deferred binding), things that will go away in GWT3. They also rely on com.google.event.dom which was built in a time where browsers needed a lot of workarounds to avoid memory leaks, make them behave similarly, etc. Both com.google.gwt.dom and com.google.event.dom could mostly be trashed in GWT3, assuming you target "modern browsers" (evergreen browsers, possibly IE11, maybe IE10, nothing older), and/or be rebuilt with a totally different architecture. In other words: they're a legacy, most probably not how we'd build things nowadays.
Finally, it's harder than necessary to integrate third-party non-GWT UI components in GWT applications; but Web Components (custom elements, etc.)
With that in mind, it doesn't make much sense (YMMV) to invest into porting widgets to GWT3. I'm not saying it won't be done, just that it's a lot of work, and nobody knows if and when it would be done. On the other hand, Web Components provide similar levels of "encapsulation" as GWT WIdgets and are portable across a lot of JS toolkits/frameworks, which means you're a) much more likely to find a component that suits your needs and b) those components, with wider reaches beyond toolkit/framework boundaries, are more likely to receive patches and overall be maintained in the long term. So, starting a new project with web components today, while not as easy as it could be in a GWT2 world –should be much better in GWT3–, interacting with them through low-level APIs (in other terms: develop a JS application, except you write Java code; like other people write TypeScript), might be your best bet for future-proofness.

It's too early to draw conclusions though, and each project will have to make their own choices.

Tuesday, January 23, 2018

Re: What is Wrong With GWT Widgets

On Monday, January 22, 2018 at 11:09:27 PM UTC+1, Mutaz Alghafary wrote:

What is exactly the problem with GWT Widgets, I am new to GWT and I have been watching some sessions about the future of GWT , it seems everyone agrees that you should not be using GWT Widgets, and use things like Elemental or other UI libraries ?

Nothing "wrong" with them, besides : they're a lot of code to maintain, sometimes quite complex, Google won't maintain them anymore, so it's big work left to the community. That doesn't mean they'll necessarily be deprecated, etc. but maintaining them has a cost.

Other reasons are: they rely on com.google.gwt.dom which makes extensive use of JSNI (and deferred binding), things that will go away in GWT3. They also rely on com.google.event.dom which was built in a time where browsers needed a lot of workarounds to avoid memory leaks, make them behave similarly, etc. Both com.google.gwt.dom and com.google.event.dom could mostly be trashed in GWT3, assuming you target "modern browsers" (evergreen browsers, possibly IE11, maybe IE10, nothing older), and/or be rebuilt with a totally different architecture. In other words: they're a legacy, most probably not how we'd build things nowadays.

Finally, it's harder than necessary to integrate third-party non-GWT UI components in GWT applications; but Web Components (custom elements, etc.)

With that in mind, it doesn't make much sense (YMMV) to invest into porting widgets to GWT3. I'm not saying it won't be done, just that it's a lot of work, and nobody knows if and when it would be done. On the other hand, Web Components provide similar levels of "encapsulation" as GWT WIdgets and are portable across a lot of JS toolkits/frameworks, which means you're a) much more likely to find a component that suits your needs and b) those components, with wider reaches beyond toolkit/framework boundaries, are more likely to receive patches and overall be maintained in the long term. So, starting a new project with web components today, while not as easy as it could be in a GWT2 world –should be much better in GWT3–, interacting with them through low-level APIs (in other terms: develop a JS application, except you write Java code; like other people write TypeScript), might be your best bet for future-proofness.

It's too early to draw conclusions though, and each project will have to make their own choices.

Re: external javascript library

Hi,

You can find more examples with JsInterop on https://gwt.zeef.com/awesomegwt#block_104342_jsinterop-wrapper. It is a list of existing JsInterop wrapper with links to the sources on GitHub or Bitbucket.

Stas

On Wednesday, January 17, 2018 at 10:34:32 AM UTC+1, Jens wrote:

but it's use is discouraged because future versions of GWT will not support it anymore. The replacement is called JsInterop and you can get an in-depth overview at

https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit

Just seen that the GWT homepage also has a short page about JsInterop: http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJsInterop.html

-- J.

Re: What is Wrong With GWT Widgets

There's really nothing wrong with widgets per se, they work fine.

The reason our community is saying to stay away from them (i.e. don't use them for new development) is because the parts of GWT that make them possible will be deprecated in the future. Nobody really knows when that will be--if I had to guess, it's at least a couple of years into the future. Also, some could be a bit heavier (use/produce more html/css/js) compared to using simply html/elemental.

On Monday, January 22, 2018 at 3:09:27 PM UTC-7, Mutaz Alghafary wrote:

What is exactly the problem with GWT Widgets, I am new to GWT and I have been watching some sessions about the future of GWT , it seems everyone agrees that you should not be using GWT Widgets, and use things like Elemental or other UI libraries ?

Re: What is Wrong With GWT Widgets

GWT Widgets are heavy and will probably be dropped in the GWT 3 (there was some talk about WC).

AFAIK Widgets wore the solution for the browser memory leaks, which are no longer a problem in modern browsers - http://www.gwtproject.org/articles/dom_events_memory_leaks_and_you.html

Dne ponedeljek, 22. januar 2018 23.09.27 UTC+1 je oseba Mutaz Alghafary napisala:

What is exactly the problem with GWT Widgets, I am new to GWT and I have been watching some sessions about the future of GWT , it seems everyone agrees that you should not be using GWT Widgets, and use things like Elemental or other UI libraries ?

Monday, January 22, 2018

Using EventBus on Android

Hi, I'm developing an app in Java and using GWT for the web build (and MOE for iOS). I'm wondering if its possible to use any of the GWT base libraries (specifically the EventBus right now) within the cross-platform portion of the code. My project uses gradle for setup, and already has gwt integrated for the web portion, but I can't seem to get this working with with the other modules.

Eclipse fails to serve CSS file

My GWT application development ran into a problem that poses a challenge to resolve. The application is developed with GWT 2.7.0 and a pilot is running at PeruseLabs (the Pilot Screen clip is below). This application has been in development for quite some months. However, in development the CSS file PeruseLabs.css doesn't seem to be loading (I don't see any evidence that it's loading). This started happening since mid January 2018. The CSS (class icon) loads as expected in the pilot <img class="icon responsive-img" src="images/bonds/singleBond.svg"> but not in development (Dev Screen clip all the way down). To reiterate - when this project is built and deployed in "prod" it works as expected. The development has come to a screeching halt though.

The corresponding icon class is

.icon {

width: 45px;

margin: 7px;

border-radius: 5px;

cursor: pointer;

}

My development environment is -

Java 8 (Ver 1.8.0_151)

Eclipse Oxygen

GWT 2.7.0

GWT Eclipse Plugin: Version 3.0

Any idea what could be wrong? Thank you in advance.

Pilot Screen clip

Dev Screen clip

What is Wrong With GWT Widgets

What is exactly the problem with GWT Widgets, I am new to GWT and I have been watching some sessions about the future of GWT , it seems everyone agrees that you should not be using GWT Widgets, and use things like Elemental or other UI libraries ?

Thursday, January 18, 2018

How to evaluate MouseWheelEvent according up/down, left/right

Hello,

I added a MouseWheelListener to a canvas-object and it works not as expected:

With firefox I get no MouseWheelEvents at all. Why?
With IE I only get MouseWheelEvents for rolling the wheel up and down. But often it is possible to move the mouse wheel to left and right with the meaning of scrolling left and right. When I move the mouse wheel to left and right I get no events. Why?
With Chrome I get MouseWheelEvents for the four directions. But the MouseWheelEvent for up and left contains the same data (also for down and right) so I do not know what the user has done. Are there other events? Or...

My goal is to know, if the mousewheel was rolled up, down or moved left, right under firefox, IE and Chrome. How to do that?

Thanks in advance

Re: JUnit changes from 2.7 to 2.8

I fixed the issue with the GWT plugin and was able to set the -devMode flag as a VM Argument.

It now works.

Thanks for the help.

On Wednesday, 17 January 2018 17:36:12 UTC, Byron Ludwig wrote:

Thanks for the reply.

Do you know how I add those in Eclipse? I also note that I cannot edit the arguments in Eclipse as there is an existing issue:
https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/168

Is there another way to set these?

On Wednesday, 17 January 2018 16:12:20 UTC, Thomas Broyer wrote:

On Wednesday, January 17, 2018 at 5:07:46 PM UTC+1, Byron Ludwig wrote:
Hi,

Could someone please explain how GWT now compiles and runs JUnit test cases as I have just upgraded my code base from 2.7 to 2.8.2 and now none of my GWT test cases work.
What has changed between releases? I can now see it trys to compile the project like a normal startup and this never occurred before.

See http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_RC1
Specifically, in the "deprecations" section: "Classic dev mode deprecated.You can switch back to dev mode for your test cases temporarily by passing gwt.args='-devMode'."

Everything else is working after upgrading and my application compiles and runs perfectly fine, just not the test cases.

Here is the exception I am getting but I cannot make heads or tails where the actual error is?

Try passing -strict (or -failOnError) and/or -draft in the gwt.args system property.

Any help is appreciated.

17/01/18 14:55:04 INFO [main org.eclipse.jetty.util.log] Logging initialized @1620ms
17/01/18 14:55:04 INFO [main org.eclipse.jetty.server.Server] jetty-9.2.14.v20151106
17/01/18 14:55:04 INFO [main /] No Spring WebApplicationInitializer types detected on classpath
17/01/18 14:55:05 INFO [main org.eclipse.jetty.server.handler.ContextHandler] Started c.g.g.j.@5d534f5d{/,
file:/C:/Users/test/workspaceGWT28/fractalsGWT/www-test/,
AVAILABLE}{C:\Users\test\workspaceGWT28\fractalsGWT\www-test}
17/01/18 14:55:05 INFO [main org.eclipse.jetty.server.ServerConnector] Started ServerConnector@78452606{HTTP/1.1}{0.0.0.0:61672}
17/01/18 14:55:05 INFO [main org.eclipse.jetty.server.Server] Started @2373ms
Compiling module com.alaric.gwt.framework.client.gwttestcase.GwtTestModule.JUnit
Ignored 190 units with compilation errors in first pass.
Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.
Compiling 1 permutation
Compiling permutation 0...
[ERROR] An internal compiler exception occurred
com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit.
at com.google.gwt.dev.js.ast.JsVisitor.translateException(JsVisitor.java:482)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:469)
at com.google.gwt.dev.js.ast.JsVisitor.doAcceptList(JsVisitor.java:450)
at com.google.gwt.dev.js.ast.JsVisitor.acceptList(JsVisitor.java:113)
at com.google.gwt.dev.js.ast.JsInvocation.traverse(JsInvocation.java:89)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsExprStmt.traverse(JsExprStmt.java:42)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAcceptWithInsertRemove(JsVisitor.java:461)
at com.google.gwt.dev.js.ast.JsVisitor.acceptWithInsertRemove(JsVisitor.java:121)
at com.google.gwt.dev.js.ast.JsBlock.traverse(JsBlock.java:53)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsProgramFragment.traverse(JsProgramFragment.java:41)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsProgram.traverse(JsProgram.java:120)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JavaScriptVerifier.verifyGlobalNameOrdering(JavaScriptVerifier.java:93)
at com.google.gwt.dev.js.ast.JavaScriptVerifier.verify(JavaScriptVerifier.java:36)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:434)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:50)
at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.AssertionError: $intern_8276 reference found before definition.
at com.google.gwt.dev.js.ast.JavaScriptVerifier$2.endVisit(JavaScriptVerifier.java:89)
at com.google.gwt.dev.js.ast.JsNameRef.traverse(JsNameRef.java:113)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
... 30 more
[ERROR] at Unknown(0): Vvl
com.google.gwt.dev.js.ast.JsNameRef
[ERROR] at SearchQuickDetailPresenterImpl.java(64): Hji(4422,
814,
Vvl)
com.google.gwt.dev.js.ast.JsInvocation
[ERROR] at SearchQuickDetailPresenterImpl.java(64): Hji(4422,
814,
Vvl)
com.google.gwt.dev.js.ast.JsExprStmt
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): var mvl = 'MessageModel.java:',
nvl = 'MessageActivateRequest.java:',
ovl = 'MessageCreateRequest.java:',
pvl = 'MessageListGridRequest.java:',
qvl = 'MessageReadRequest.java:',
rvl = 'MessageUpdateRequest.java:',
svl = 'MessageActivateResponse.java:',
tvl = 'MessageContextResponse.java:',
uvl = 'MessageCreateResponse.java:',
vvl = 'MessageDeleteResponse.java:',
wvl = 'MessageReadResponse.java:',
xvl = 'MessageUpdateResponse.java:',
yvl = 'MessageEditorPresenterImpl.java:',
zvl = 'MessageDetailsPresenterImpl.java:',
Avl = 'MessageContentPresenterImpl.java:',
Bvl = 'MessageTransportPresenterImpl.java:',
Cvl = 'MessageTemplate.java:',
Dvl = 'includeTemplateName',
Evl = 'VerticalMessageContext.java:',
Fvl = 'com.alaric.gwt.framework.client.presenter.editor.message',
Gvl = 'MessageContentViewImpl.java:',
Hvl = 'MessageContentFieldViewImpl.java:',
Ivl = 'MessageContentFieldPresenterImpl.java:',
Jvl = 'RichTextArea.java:',
Kvl = 'TransactionFieldProviderImpl.java:',
Lvl = 'com.alaric.gwt.framework.client.presenter.editor.message.content',
Mvl = 'com.alaric.gwt.framework.client.presenter.editor.message.content.field',
Nvl = 'com.alaric.gwt.framework.client.presenter.editor.message.content.field.transaction',
Ovl = 'MessageDetailsViewImpl.java:',
Pvl = 'com.alaric.gwt.framework.client.presenter.editor.message.details',
Qvl = 'com.alaric.gwt.framework.client.presenter.editor.message.details.users',
Rvl = 'UserTableWithButtonsPresenterImpl.java:',
Svl = 'com.alaric.gwt.framework.client.presenter.editor.message.transport',
Tvl = 'com.alaric.gwt.framework.client.presenter.editor.message.transport.swaptable',
Uvl = 'TransportMessageTableWithButtonsPresenterImpl.java:',
Wvl = 'MessageManagerPresenterImpl.java:',
_vl = ' messages?',
bwl = 'com.alaric.gwt.framework.client.view.editor.message',
cwl = 'MessageEditorViewImpl.java:',
dwl = 'RichTextAreaImplStandard.java:',
ewl = 'MessageContentViewImpl_MessageContentViewImplUiBinderImpl.java:',
fwl = 'com.alaric.gwt.framework.client.view.editor.message.component.content',
gwl = 'MessageContentViewImpl_MessageContentViewImplUiBinderImpl_GenBundle_default_InlineClientBundleGenerator.java:',
hwl = 'Placeholder fields',
iwl = 'AbstractTextWithStyleAndDoubleClickRightClickColumn.java:',
kwl = 'MessageContentFieldViewImpl_MessageContentFieldViewImplUiBinderImpl.java:',
lwl = 'com.alaric.gwt.framework.client.view.editor.message.component.content.fields',
mwl = 'MessageContentFieldViewImpl_MessageContentFieldViewImplUiBinderImpl_GenBundle_default_InlineClientBundleGenerator.java:',
nwl = 'MessageDetailsViewImpl_MessageDetailsViewImplUiBinderImpl.java:',
owl = 'com.alaric.gwt.framework.client.view.editor.message.component.details',
pwl = 'com.alaric.gwt.framework.client.view.editor.message.component.details.users',
qwl = 'com.alaric.gwt.framework.client.view.editor.message.component.details.users.table',
rwl = 'UserDescriptor.java:',
swl = 'UserTableViewImpl.java:',
twl = 'MessageTransportViewImpl.java:',
uwl = 'MessageTransportViewImpl_MessageProviderViewImplUiBinderImpl.java:',
vwl = 'com.alaric.gwt.framework.client.view.editor.message.component.transport',
wwl = 'Configured Message Transports',
xwl = 'MessageTransportViewImpl_MessageProviderViewImplUiBinderImpl_TemplateImpl.java:',
ywl = 'com.alaric.gwt.framework.client.view.editor.message.component.transport.swaptable',
zwl = 'com.alaric.gwt.framework.client.view.editor.message.component.transport.swaptable.table',
Awl = 'DescriptionColumn.java:',
Bwl = 'com.alaric.gwt.framework.client.view.library.keyvaluetablewithbuttons.cell',
Cwl = 'EmptyColumn.java:',
Dwl = 'KeyColumn.java:',
Ewl = 'com.alaric.gwt.framework.client.view.manager.message',
Fwl = 'MessageDeleteRequest.java:',
Gwl = 'MessageTemplateContext.java:',
Hwl = 'RichTextAreaImpl.java:',
Iwl = 'RichTextAreaImplMozilla.java:';
function fv(a){
var b,
c;
B6i[b = ++C6i] = fv;
(D6i[b] = R7i + S9i ,
!(D6i[b] = ctj + '2342' ,
a).xd) && ((D6i[b] = ctj + '2343' ,
a).xd = new r$b(a));
c = (D6i[b] = ctj + '2346' ,
a).xd;
[...]
}

function gv(a){
var b,
c;
B6i[b = ++C6i] = gv;
(D6i[b] = R7i + S9i ,
!(D6i[b] = ctj + '2406' ,
a).yd) && ((D6i[b] = ctj + '2407' ,
a).yd = new M$b(a));
c = (D6i[b] = ctj + '2410' ,
a).yd;
[...]
}

function hv(a){
var b,
c;
B6i[b = ++C6i] = hv;
(D6i[b] = R7i + S9i ,
!(D6i[b] = ctj + '2470' ,
a).zd) && ((D6i[b] = ctj + '2471' ,
a).zd = new R$b(a));
c = (D6i[b] = ctj + '2474' ,
a).zd;
[...]
}

[...]

com.google.gwt.dev.js.ast.JsGlobalBlock
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): <JsProgramFragment>
com.google.gwt.dev.js.ast.JsProgramFragment
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): <JsProgram>
com.google.gwt.dev.js.ast.JsProgram
[ERROR] Unrecoverable exception,
shutting down
com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
at com.google.gwt.dev.javac.CompilationProblemReporter.logAndTranslateException(CompilationProblemReporter.java:106)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:459)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:50)
at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
at java.lang.Thread.run(Unknown Source)
[ERROR] Not all permutation were compiled ,
completed (0/1)
[ERROR] Compiler aborted with an exception
com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
at com.google.gwt.dev.PermutationWorkerFactory$Manager.doRun(PermutationWorkerFactory.java:166)
at com.google.gwt.dev.PermutationWorkerFactory$Manager.run(PermutationWorkerFactory.java:106)
at com.google.gwt.dev.PermutationWorkerFactory.compilePermutations(PermutationWorkerFactory.java:257)
at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:211)
at com.google.gwt.dev.Compiler.compile(Compiler.java:219)
at com.google.gwt.dev.Compiler.compile(Compiler.java:155)
at com.google.gwt.junit.JUnitShell.compileForWebMode(JUnitShell.java:1102)
at com.google.gwt.junit.JUnitShell.maybeCompileForWebMode(JUnitShell.java:1167)
at com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl2(CompileStrategy.java:183)
at com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl(CompileStrategy.java:113)
at com.google.gwt.junit.SimpleCompileStrategy.maybeCompileModule(SimpleCompileStrategy.java:36)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1358)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1326)
at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:682)
at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)