Elemental2 provides type-checked access to browser APIs for Java
code. This is done by using closure extern files and generating
JsTypes, which are part of the new JsInterop specification that
is implemented in both GWT and J2CL.
https://github.com/google/elemental2
This is an unofficial release
I understand that GWT 2.8.2 supports translation of Java 8 syntax, and not
Java 11.
But I thought there might be a good chance that could use Java 11 features
on the server (e.g. Jetty) that responds to GWT-RPC requests.
This works fine in deployment mode: Mark the project as Java 11 in Maven,
This is again a case where splitting client and server code into separate
Maven modules will help (see
https://github.com/tbroyer/gwt-maven-archetypes/).
The problem here is (probably) that GWT tries to load the compiled classes,
and can't because it doesn't understand Java 11 bytecode.
So
Hello, I've got the very same situation but in the different environment.
I think perhaps it is because old version of jetty(9.2) is embedded in
gwt-dev.jar(2.3.2). This version of jetty doesn't seem to run on Java9
or later.
So you should exclude org.eclipse.jetty package from gwt-dev.jar
Thanks Yuichi,
It turns out in the Super Dev Mode UI in the Jetty tab there was an error
that Jetty couldn't start, and clicking on that showed me the stack
backtrace in the bottom half of the window, and indeed it was some
annotation processing problem with Jetty (common problem with older
Hello Thomas,
Thanks for the answer about splitting the Maven modules. That worked great!
In case anyone else is trying it, here's what I did:
- Used the "mvn archetype:generate" from the
link https://github.com/tbroyer/gwt-maven-archetypes/ with the artifact
"modular-webapp"
- In
