Google Web Toolkit

Tuesday, December 16, 2025

Re: GWT and Payara 6 – javax.servlet vs jakarta.servlet Compatibility Issue

And if you switch to use Maven, this is what you need: https://central.sonatype.com/artifact/org.gwtproject/gwt-servlet-jakarta

On Wednesday, 17 December 2025 at 2:11:41 am UTC+11 Colin Alworth wrote:

Note that the one extra step to use the "...rpc.jakarta.RemoteServiceServlet" class is to replace your gwt-servlet artifact with the gwt-servlet-jakarta one. You'll naturally need to update your ant/eclipse configuration to point to these jars, first included in GWT 2.11.0 https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0

On Tuesday, December 16, 2025 at 9:08:46 AM UTC-6 dav...@googlemail.com wrote:
hi Pankaj

My project is currently using GWT 2.12.1

I create a servelet thus::

import com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet;

Everything *just works*

I'll take this opportunity to say what a fantastic job has been done over the years with GWT. My project was created early this century. I had my nose in an already out of date GWT book (hard copy) and from that used some methods that were already deprecated. Nothing much has been altered over 20 odd years apart from upgrades to the GWT version. I cannot remember much hassle - fantastic job by the devs :-) I wish other projects would follow such a smooth path.

On Tuesday, 16 December 2025 at 11:00:38 UTC Pankaj Kumar wrote:
Dear GWT Community,

We are currently upgrading our application to the latest GWT version using an Eclipse plugin–based, Ant-managed project.

After creating a sample GWT project and deploying it on Payara Server 6, we encounter deployment errors related to the Servlet API (javax.servlet).

After analysis, we observed that:

The latest GWT version still depends on javax.servlet

However, Payara 6 and newer Java/Jakarta EE versions require jakarta.servlet

Due to this mismatch, the application fails during deployment on Payara 6.

Could you please guide us .

Best Regards,
Pankaj Kumar
Java Developer

--
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/00894826-62f0-4072-8c88-7b9827d2ac29n%40googlegroups.com.

Re: GWT and Payara 6 – javax.servlet vs jakarta.servlet Compatibility Issue

Note that the one extra step to use the "...rpc.jakarta.RemoteServiceServlet" class is to replace your gwt-servlet artifact with the gwt-servlet-jakarta one. You'll naturally need to update your ant/eclipse configuration to point to these jars, first included in GWT 2.11.0 https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0

On Tuesday, December 16, 2025 at 9:08:46 AM UTC-6 dav...@googlemail.com wrote:

hi Pankaj

My project is currently using GWT 2.12.1

I create a servelet thus::

import com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet;

Everything *just works*

I'll take this opportunity to say what a fantastic job has been done over the years with GWT. My project was created early this century. I had my nose in an already out of date GWT book (hard copy) and from that used some methods that were already deprecated. Nothing much has been altered over 20 odd years apart from upgrades to the GWT version. I cannot remember much hassle - fantastic job by the devs :-) I wish other projects would follow such a smooth path.

On Tuesday, 16 December 2025 at 11:00:38 UTC Pankaj Kumar wrote:
Dear GWT Community,

We are currently upgrading our application to the latest GWT version using an Eclipse plugin–based, Ant-managed project.

After creating a sample GWT project and deploying it on Payara Server 6, we encounter deployment errors related to the Servlet API (javax.servlet).

After analysis, we observed that:

The latest GWT version still depends on javax.servlet

However, Payara 6 and newer Java/Jakarta EE versions require jakarta.servlet

Due to this mismatch, the application fails during deployment on Payara 6.

Could you please guide us .

Best Regards,
Pankaj Kumar
Java Developer

--
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/4b45df8b-593a-4f11-996c-1b06e798f60en%40googlegroups.com.

Re: GWT and Payara 6 – javax.servlet vs jakarta.servlet Compatibility Issue

hi Pankaj

My project is currently using GWT 2.12.1

I create a servelet thus::

import com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet;

Everything *just works*

I'll take this opportunity to say what a fantastic job has been done over the years with GWT. My project was created early this century. I had my nose in an already out of date GWT book (hard copy) and from that used some methods that were already deprecated. Nothing much has been altered over 20 odd years apart from upgrades to the GWT version. I cannot remember much hassle - fantastic job by the devs :-) I wish other projects would follow such a smooth path.

On Tuesday, 16 December 2025 at 11:00:38 UTC Pankaj Kumar wrote:

Dear GWT Community,

We are currently upgrading our application to the latest GWT version using an Eclipse plugin–based, Ant-managed project.

After creating a sample GWT project and deploying it on Payara Server 6, we encounter deployment errors related to the Servlet API (javax.servlet).

After analysis, we observed that:

The latest GWT version still depends on javax.servlet

However, Payara 6 and newer Java/Jakarta EE versions require jakarta.servlet

Due to this mismatch, the application fails during deployment on Payara 6.

Could you please guide us .

Best Regards,
Pankaj Kumar
Java Developer

--
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/821a70ce-f9d3-4da3-bf30-65fada0099d2n%40googlegroups.com.

GWT and Payara 6 – javax.servlet vs jakarta.servlet Compatibility Issue

Dear GWT Community,

We are currently upgrading our application to the latest GWT version using an Eclipse plugin–based, Ant-managed project.

After creating a sample GWT project and deploying it on Payara Server 6, we encounter deployment errors related to the Servlet API (javax.servlet).

After analysis, we observed that:

The latest GWT version still depends on javax.servlet
However, Payara 6 and newer Java/Jakarta EE versions require jakarta.servlet

Due to this mismatch, the application fails during deployment on Payara 6.

Could you please guide us .

Best Regards,
Pankaj Kumar
Java Developer

--
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/0832f6d0-07b0-4ee9-bab1-b1269cb0b828n%40googlegroups.com.

Thursday, December 11, 2025

Re: GWT project using Github codespaces

The file is https://github.com/gwtproject/gwt/blob/main/dev/codeserver/java/com/google/gwt/dev/codeserver/stub.nocache.js and as you can see your only option would be to replace the file (try copying it into your source tree at the very same location) as the logic cannot be configured.

Otherwise you might be able to use a browser plugin like requestly which allows you to redirect HTTP calls transparently.

https://docs.requestly.com/general/http-rules/rule-types/redirect-rule

-- J.

jamal....@gmail.com schrieb am Donnerstag, 11. Dezember 2025 um 13:38:09 UTC+1:

Hi,
I am testing Github codespaces IDE and check if I can use it and if it works with GWT setup. I use gwt-maven-archetypes 'modular-webapp'. I start codeserver then jetty server. The problem is in Github codespaces codeserver is accessible at a URL that is different from the default. Example:
Codeserver URL: https://example-app-some-random-string-9876.app.github.dev
Jetty container URL: https://example-app-some-random-string-8080.app.github.dev

So the problem app.nocache.js generates nocacheUrl as 'https://example-app-some-random-string-8080.app.github.dev:9876' where it should be 'https://example-app-some-random-string-9876.app.github.dev'

Is there a way I cam make app.nocache.js generate the desired URL?

Thanks

--
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/5de55b27-db71-455a-9d60-2568ae4f12cdn%40googlegroups.com.

GWT project using Github codespaces

Hi,

I am testing Github codespaces IDE and check if I can use it and if it works with GWT setup. I use gwt-maven-archetypes 'modular-webapp'. I start codeserver then jetty server. The problem is in Github codespaces codeserver is accessible at a URL that is different from the default. Example:
Codeserver URL: https://example-app-some-random-string-9876.app.github.dev

Jetty container URL: https://example-app-some-random-string-8080.app.github.dev

So the problem app.nocache.js generates nocacheUrl as 'https://example-app-some-random-string-8080.app.github.dev:9876' where it should be 'https://example-app-some-random-string-9876.app.github.dev'

Is there a way I cam make app.nocache.js generate the desired URL?

Thanks

--
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/55c95a11-44ff-40ad-af2c-c22e5d6e596bn%40googlegroups.com.

Wednesday, December 10, 2025

Re: JsInterop wrapping of D3 js

On Wednesday, December 10, 2025 at 9:09:13 PM UTC+1 David Nouls wrote:

From what I remember, Google stopped GWT during the time of the conflict between SUN and Microsoft. They had litigation going on around the Java support in IE. I always was under the impression that Google was trying to protect themselves against SUN for the same reason.

Why would they have developed J2Cl then? It doesn't make sense.

My recollection is that the people doing frontend work knew JS and CSS and Closure and didn't want to change (and it was probably a bit hard to hire for GWT), so the goal was to translate Java to JS to produce a JS lib, with Closure typing, for use with their existing pipeline. They initially tried to add it to GWT proper (IIRC that's how they did it in Inbox at the time), but it wasn't conclusive.

Also, their frontend pipeline for Closure is full of optimizations around updates, where browsers only download a "diff" of what changed since the version they had in cache. GWT is duplicating many of those things that they already had, and probably isn't as good. Also the fact that GWT is kind of a "monolithic" build pipeline.

--
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/3933ee79-3afc-4a5b-8d58-98c631e5c4ean%40googlegroups.com.