Re: Announcing GWT 2.10.1 and 2.11 releases

[Adrian Smith]

Thanks for all the work you put in to GWT! Much appreciated! Really looking 
forward to the improved Collections support myself.

On Wednesday, January 10, 2024 at 12:30:29 PM UTC+1 Giuseppe La Scaleia 
wrote:

> Great work guys.
>
>
> Giuseppe La Scaleia
> CNR - IMAA
> geoSDI
> Sviluppo Software
>
> C.da S. Loja
> 85050  Tito Scalo - POTENZA (PZ)
> Italia
>
> phone:  +39 0971427305 <+39%200971%20427305>
> fax:  +39 0971 427271 <+39%200971%20427271>
> mob:+39 331 2174998 <+39%20331%20217%204998>
> mail: glasc...@gmail.com
> skype:  glascaleia
>
> web: https://www.geosdi.org
>
>
>  
>
>
> Il giorno mar 9 gen 2024 alle ore 22:36 Colin Alworth <
> co...@colinalworth.com> ha scritto:
>
>> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
>> second release under the new groupId, be sure when you update to change 
>> away from "com.google.gwt", as it will not get more updates.
>>
>> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
>> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
>> vulnerable projects are aware of any problem, compile warnings will be 
>> emitted if a problem is detected, and the server will default to not 
>> allowing any vulnerable RemoteService instances. See 
>> https://github.com/gwtproject/gwt/issues/9709 for information on the 
>> issue, how we're responding to it, and how any additional follow-up might 
>> look.
>>
>> Other highlights:
>>
>>- Transitioned to GitHub pull requests for new contributions, with 
>>nightly builds running on GitHub Actions.
>>- Added release artifacts for jakarta.servlet packages for both 
>>RequestFactory and GWT-RPC.
>>- Tested support for running on Java 21. This is likely to be the 
>>final minor release series to support running on Java 8.
>>- Updated JRE emulation to support Java 11 for Collections, streams, 
>>and more.
>>
>> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
>> complete release notes.
>>
>> This release wouldn't have been possible without help from so many 
>> contributors, including developers, testers, and sponsors. A short list of 
>> the teams and individuals that directly brought us this release: Juan Pablo 
>> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
>> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
>> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
>> Insurance Insight Inc. Join us on the issue tracker 
>>  or at our OpenCollective page 
>>  to help make future releases 
>> possible.
>>
>> -- 
>>
> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/17887d7a-ee71-4dd6-bd21-8365a91536dbn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/ee846b70-de18-476f-aa41-0f7f5aa5ffben%40googlegroups.com.

Re: GWT 2.9.0 release

[Adrian Smith]

Thanks for the incredible amount of work you put into GWT, and for this 
release. Just tried it out, enjoyed replacing Lombok "var" with proper Java 
"var" :-)

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/d6687a9b-809b-4f22-8c8a-749a70f04aa7%40googlegroups.com.

Re: GWT 2.8.2 and IntelliJ IDEA

[Adrian Smith]

Hello,

I use IntelliJ although I must admit I start the application on the 
command-line as opposed to using IntelliJ to do this.

I have found the command

mvn -Djetty.version=9.4.19.v20190610 war:exploded gwt:devmode


work well for me.

To debug server-side code, in the GWT Maven plugin in pom.xml, I use:

  
net.ltgt.gwt.maven
gwt-maven-plugin
1.0-rc-10
...

  ...
  

-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8425
  
  ...

  

And then connect to that port using IntelliJ's debugger.

I hope that helps!

On Monday, 16 March 2020 12:07:54 UTC+1, Mark Fekete wrote:
>
> HI all,
>
> I wonder if anyone is using Intellij and GWT 2.8.2. I 've literally found 
> nothing about this topic.
>
>
> My problem is that whenever i want to start and debug my application, it 
> fails because the buildin Jetty-server runs with the wrong version 9.2 
> instead of 9.4.
>
> The solution is to use a run configuration with a dedicated Jetty server. 
> This is possible  with the "Jetty Runner"-IntelliJ-Plugin which uses Jetty 
> version 9.4. 
> Unfortunately, when I run this configuration in the context of my GWT 
> 2.8.2 project, for some reasons the wrong jetty version is started: 9.2 
> which is located somewher in gwt-dev-xxx.jar
>
> Any idea how to fix this? Or I'm forced to switch to Eclipse?
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/042d91e3-a127-4148-b2de-372227c366b4%40googlegroups.com.

java.time

[Adrian Smith]

Please excuse me if this topic has been discussed before. I did look but I 
didn't find anything recent.

I was looking to use java.time with GWT. I saw it was not supported "out of 
the box" in 2.8.2. I looked around for libraries and 
found https://github.com/m-m-m/gwt-time. It was not complete, but I fixed a 
few things and it worked well enough for me.

What do you use for java.time? Do you use that library, or something else?

The original maintainer of the m-m-m project was helpful, but not 
interested in continuing maintenance. I have offered to take offer this 
project, so now it lives in my GitHub repository.

This is my understanding of the situation:

   - The code originated from another project, but is used with permission.
   - The code is copyright some other people, therefore, I imagine it 
   cannot be merged with GWT core.
   - There is a lot missing:
  - I'm not convinced all classes are implemented? The ones I was 
  looking for are implemented, but there might be others that are not.
  - It was never designed for GWT so it uses concurrent maps in some 
  place (easy enough to replace with normal maps), java.util.Locale in some 
  places.
  - It doesn't have converters to allow seriazliation of the types from 
  client to the server.
  - There are no tests
   - The code is not currently on Maven Central. The procedure is checking 
   out from Git, doing "mvn install", then using it. I would be happy to 
   publish it to Maven Central if there was interest.
   - The current version numbering mirrors GWT, so it's currently 
   "2.8.2-SNAPSHOT". I'm not sure this is really helpful.

So I am going to slowly improve the code for my usage (i.e. where my 
project needs a class or encounters a bug, I will make the change and 
publish it). I have added the facility for LocalDate to be sent between the 
client and the server (that is the only class I need at the moment) so 
adding client-server communication for other classes should be easy too.

I welcome your thoughts. You are welcome to use it, and of course pull 
requests are welcome too. If there is another implementation that is 
better, I am happy to abandon this repository and use (and submit pull 
requests to) the better one.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/29a58e13-914b-4cfb-b4aa-26ad63dcaa09%40googlegroups.com.

Re: super dev mode Jetty version?

[Adrian Smith]

>
>
>- Is it possible to configure my project to use Jetty 9.3.x in super 
>dev mode?
>
> In case you are still looking to an answer to this, I found out that you 
can use the following command-line options to Maven when running super dev 
mode to influence what version of Jetty is used:

mvn -Djetty.version=9.4.19.v20190610 war:exploded gwt:devmode 


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/0a4f510a-d494-4cfb-9281-fbd06a3d1cda%40googlegroups.com.

Re: Using Java 11 on the server to implement GWT-RPC services

[Adrian Smith]

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 Jetty 
versions with Java 11).

Thanks to your blog post (translation worked nicely!) I did some 
investigation. I didn't get your method to work, but I did find out that if 
I all Maven (super dev mode) with the following command-line I can get my 
original single-Maven-project to use the Jetty of my choosing, and now 
Super Dev Mode can serve Java 11 server-side code:

mvn -Djetty.version=9.4.19.v20190610 war:exploded gwt:devmode 


Adrian
 
On Wednesday, July 17, 2019 at 11:31:37 AM UTC+2, Yuichi Sugimura wrote:
>
> 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 and 
> attach newer version of jetty to classpath. 
>
> Here's my blog post(in Japanese) about this. Maybe you can use some 
> translation site. 
>
> https://www.gwtcenter.com/execute-gwt282-on-java9-or-later 
>
> Hope this helps. 
>
> On 2019/07/17 17:51, Adrian Smith wrote: 
> > 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, compile the WAR with Maven, GWT creates the JS fine, and then the 
> > Java 11 servlet container executes the WAR fine, and the server code can 
> > make use of Java 11 features. 
> > 
> > However in "super dev mode" it doesn't work, and also doesn't really 
> > give an errors (neither on the console in Maven, nor in the "Jetty" tab 
> > of the "super dev mode" console.) 
> > 
> > With a Java 11 JVM but specifying Java 8 in Maven (as is the default 
> > from the Maven archtetype), everything works fine: 
> > 
> > $ java -version 
> > openjdk version "11.0.2" 2019-01-15 
> > $ ~/Downloads/gwt-2.8.2/webAppCreator -templates maven,sample -out 
> > Foo com.mycompany.Foo 
> > 
> > $ cd Foo 
> > 
> > $ mvn clean war:exploded gwt:devmode 
> > 
> > 
> > That all works fine. 
> > 
> > However, when I change, in the pom.xml 
> > 
> > 11 
> > 11 
> > 
> > 
> > Then when I execute 
> > 
> > $ mvn clean war:exploded gwt:devmode 
> > 
> > 
> > The "super dev mode" console opens, however when I click on "Launch 
> > Default Browser" I see "503 Service Unavailable" in the browser. That 
> > error message comes from Jetty. 
> > 
> > There is a note in the "Jetty" tab of the "super dev mode" console about 
> > the 503 but just request/response headers and no further information. 
> > There is also nothing printed to the terminal console where I executed 
> > the "mvn" command. 
> > 
> > Note: I have not changed the source code at all. It's the default Maven 
> > archetype source code, which doesn't use any Java 11 syntax. 
> > 
> > I have also tried changing the 1.8 in Maven's 
> > GWT plugin section, however, as I expected, that failed immediately with 
> > a clear error message that the GWT compiler doesn't support > 1.8, which 
> > is fine. I know that's a lot of work, but I figured I could at least use 
> > Java 11 features on the server. 
> > 
> > Am I missing something simple, or is this more complex than I imagine 
> > and thus is not supported? 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4fd9fc2c-713f-40e9-9cd4-cc28d4b64372%40googlegroups.com.

Re: Using Java 11 on the server to implement GWT-RPC services

[Adrian Smith]

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 the root "pom.xml" upgraded the "jetty-maven-plugin" to the latest 
   version I found on Maven Central (I used "9.4.19.v20190610")
   - In the "server/pom.xml" added a plugin like

 
  maven-compiler-plugin
  
11
11
  


   - Followed the rest of the instructions to run the software from the 
   link above
   
This approach also has the advantage that the IDE understands that the 
"server" part is Java 11 but the "client" and "shared" sections are Java 8 
and can show appropriate syntax errors (e.g. usage of "var" keyword).

Thanks again,
Adrian

On Wednesday, July 17, 2019 at 11:12:26 AM UTC+2, Thomas Broyer wrote:
>
> 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/ 
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Ftbroyer%2Fgwt-maven-archetypes%2F=D=1=AFQjCNGvdFIpqK3Dd7AnfR9gOzz7s2ypCA>
> ).
> 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 you'll want to compile the shared and client code to Java 8 bytecode, 
> and the server-only code to Java 11 bytecode.
>
> On Wednesday, July 17, 2019 at 10:56:58 AM UTC+2, Adrian Smith wrote:
>>
>> 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, 
>> compile the WAR with Maven, GWT creates the JS fine, and then the Java 11 
>> servlet container executes the WAR fine, and the server code can make use 
>> of Java 11 features.
>>
>> However in "super dev mode" it doesn't work, and also doesn't really give 
>> an errors (neither on the console in Maven, nor in the "Jetty" tab of the 
>> "super dev mode" console.)
>>
>> With a Java 11 JVM but specifying Java 8 in Maven (as is the default from 
>> the Maven archtetype), everything works fine:
>>
>> $ java -version
>> openjdk version "11.0.2" 2019-01-15
>> $ ~/Downloads/gwt-2.8.2/webAppCreator -templates maven,sample -out Foo 
>> com.mycompany.Foo
>>
>> $ cd Foo
>>
>> $ mvn clean war:exploded gwt:devmode
>>
>>
>> That all works fine.
>>
>> However, when I change, in the pom.xml
>>
>> 11
>> 11
>>
>>
>> Then when I execute 
>>
>> $ mvn clean war:exploded gwt:devmode
>>
>>
>> The "super dev mode" console opens, however when I click on "Launch 
>> Default Browser" I see "503 Service Unavailable" in the browser. That error 
>> message comes from Jetty.
>>
>> There is a note in the "Jetty" tab of the "super dev mode" console about 
>> the 503 but just request/response headers and no further information. There 
>> is also nothing printed to the terminal console where I executed the "mvn" 
>> command.
>>
>> Note: I have not changed the source code at all. It's the default Maven 
>> archetype source code, which doesn't use any Java 11 syntax.
>>
>> I have also tried changing the 1.8 in Maven's 
>> GWT plugin section, however, as I expected, that failed immediately with a 
>> clear error message that the GWT compiler doesn't support > 1.8, which is 
>> fine. I know that's a lot of work, but I figured I could at least use Java 
>> 11 features on the server.
>>
>> Am I missing something simple, or is this more complex than I imagine and 
>> thus is not supported?
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4ce3b5f3-ef77-43fa-ba33-65fa5960fc97%40googlegroups.com.

Using Java 11 on the server to implement GWT-RPC services

[Adrian Smith]

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, 
compile the WAR with Maven, GWT creates the JS fine, and then the Java 11 
servlet container executes the WAR fine, and the server code can make use 
of Java 11 features.

However in "super dev mode" it doesn't work, and also doesn't really give 
an errors (neither on the console in Maven, nor in the "Jetty" tab of the 
"super dev mode" console.)

With a Java 11 JVM but specifying Java 8 in Maven (as is the default from 
the Maven archtetype), everything works fine:

$ java -version
openjdk version "11.0.2" 2019-01-15
$ ~/Downloads/gwt-2.8.2/webAppCreator -templates maven,sample -out Foo 
com.mycompany.Foo

$ cd Foo

$ mvn clean war:exploded gwt:devmode


That all works fine.

However, when I change, in the pom.xml

11
11


Then when I execute 

$ mvn clean war:exploded gwt:devmode


The "super dev mode" console opens, however when I click on "Launch Default 
Browser" I see "503 Service Unavailable" in the browser. That error message 
comes from Jetty.

There is a note in the "Jetty" tab of the "super dev mode" console about 
the 503 but just request/response headers and no further information. There 
is also nothing printed to the terminal console where I executed the "mvn" 
command.

Note: I have not changed the source code at all. It's the default Maven 
archetype source code, which doesn't use any Java 11 syntax.

I have also tried changing the 1.8 in Maven's 
GWT plugin section, however, as I expected, that failed immediately with a 
clear error message that the GWT compiler doesn't support > 1.8, which is 
fine. I know that's a lot of work, but I figured I could at least use Java 
11 features on the server.

Am I missing something simple, or is this more complex than I imagine and 
thus is not supported?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f3185b58-73f2-4e21-8775-bdc393e24d24%40googlegroups.com.