Re: Need Help: GWT 2.12 Migration + gwtrpc-spring-1.02 Compatibility Issue

Yes we did successfully migrate our GWT project to GWT 2.12.1 and Java17 / Jakarta.

However we didn't use gwtrpc-spring...

First thing would be analyze whether the dependency could be thrown out. If that is not possible then I did the following:

As you mentioned the repo ( nexus.emergya.es ) seems offline but the original project is still online:

Binary: https://code.google.com/archive/p/gwtrpc-spring/downloads

Source: https://code.google.com/archive/p/gwtrpc-spring/source

For several old dependencies I had to create a Java17 / Jakarta version on my own, if there was no compatible version.

https://code.google.com/archive/p/gwtrpc-spring/source/default/commits

The last changes was to mavenize the project which is a start.

So what would I do?

1) Download the source and setup a github project

2) commit the original source 1:1 (to prove your base)

3) Upgrade the project to jakarta / java 17

4) Either add or remove missing transitive dependencies (like gilead-core ...) This one could be found here: https://github.com/lmco/eurekastreams-mvn-repo/tree/master/releases/net/sf/gilead/gilead4gwt/1.3.2

5) ...

Good luck!

Frank Hossfeld schrieb am Donnerstag, 12. Juni 2025 um 08:26:37 UTC+2:

I have stopped using RPC for years now. But I would suggest to copy the one class >>SpringRemoteServiceServlet<< of gwtrpc-spring  your project and change the import from >>javax.servlet<< to >>jakarta.servlet<< and of course, remove the dependency.

Arpan Ameta schrieb am Mittwoch, 11. Juni 2025 um 14:59:41 UTC+2:

We're currently migrating our legacy project from GWT 2.8.1 to GWT 2.12.0 to be compatible with JDK 17 and modern tooling. As part of this upgrade, we've updated the dependency from:

<dependency>
    <groupId>org.gwtrpcspring</groupId>
    <artifactId>gwtrpc-spring</artifactId>
    <version>1.01</version>
</dependency>

To :

<dependency>
    <groupId>org.gwtrpcspring</groupId>
    <artifactId>gwtrpc-spring</artifactId>
    <version>1.02</version>
</dependency>

We're facing the following challenges:

• Deployment fails in WildFly 33, throwing NoClassDefFoundError for javax.servlet.http.HttpServlet, which seems to originate from RemoteServiceServlet in the GWT RPC stack.

• The artifact gwtrpc-spring:1.02 isn't resolving from Maven Central, and the old configured repo http://www.mvnsearch.org/maven2/ is timing out.

• We're unsure if gwtrpc-spring 1.02 is compatible with GWT 2.12 and Jakarta EE 9+ (jakarta.servlet) changes.

📌 Has anyone successfully used gwtrpc-spring with GWT 2.12 and JDK 17?
📌 Any fork or alternative for gwtrpc-spring compatible with modern GWT and WildFly?
📌 Suggestions on resolving servlet dependencies (HttpServlet) when deploying in WildFly 33?

Any help, pointers, or even working examples would be greatly appreciated! 🙏

Thanks in advance!
— Arpan

--
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/74f4738a-4ac9-4abb-87d6-3e124ef43ac1n%40googlegroups.com.