Moving to jakarta from javax

[Moshe]

Hello,

Are the Jakarta JARs what we need to use when moving to Tomcat 10? I was verifying but the servlet Jakarta sources jar has only some of the sources. So I decompiled some classes in gwt-servlet-jakarta.jar and I still see javax in imports. 

Thanks. 

[Craig Mitchell]

Yes.  Add this:  https://mvnrepository.com/artifact/org.gwtproject/gwt-servlet-jakarta

[Craig Mitchell]

My comment probably doesn't help much.  I'm not sure how GWT extracts the Jakarta stuff for the library build.  I think it's all in here: https://github.com/gwtproject/gwt

In any case, adding GWT Servlet Jakarta should just work for Tomcat 10 (it did for me).

<dependency>
  <groupId>org.gwtproject</groupId>
  <artifactId>gwt-servlet-jakarta</artifactId>
</dependency>

[Colin Alworth]

The gwt-servlet-jakarta.jar is the one you want for using GWT-RPC in jakarta.servlet environments. Which classes that you need are not updated correctly?

The one (deliberate) omission I'm aware of is validation, but there is no server-side validation component for GWT. However, you may not be able to serialize validation types over gwt-rpc (though it is unlikely you were using this feature) though, since the built-in GWT implementation of validation is frozen at 1.0.0.GA - you'll need a different client implementation, and that implementation will need to be serializable over GWT-RPC to use in this way. See https://gitlab.com/ManfredTremmel/gwt-bean-validators and https://github.com/gwtproject/gwt/issues/9844.

[Moshe]

I wanted to be certain I was on the right path and it was possible. Of course,  moving to Tomcat 10x requires updating Spring among other things like Filters. 

[Moshe]

Just one follow up note. Jakarta jars worked fine with Tomcat 9x. No problems making RPC calls. 

On Monday, September 30, 2024 at 6:39:02 AM UTC-7 Colin Alworth wrote: