We also moved a long time ago from RPC to JERSEY JSON REST (which, btw, throws serialized runtime exceptions as JSON with a status 400 for consuming client side…).
I'm currently thinking that due to time constraints that forking gwt-jackson and resty-gwt, gradle-ifying, and using as git submodules is my only way forwards. I can at least update resty-gwt to use the jakarta annotation namespace instead of the javax annotation namespace.
Is there a documented path forwards if I wanted to look into the feasibility of switching from GWT.create to Annotation code generation? At least for client side gwt-jackson ObjectMapper instances?
I checked for "forks" to see if anyone had been putting any work in to the legacy code to bring it up to date some, but the forks list for rest-gwt says 168 with zero displayed as accessible? Similar for gwt-jackson with 57 forks and zero displayed as accessible?
We keep running into issues on a continuous basis trying to migrate from resty-gwt/gwt-jackson to domino-rest/domino-jackson as our code is full of annotations and path parameter values that worked with gwt-jackson/resty-gwt that aren't compatible with domino-jackson/domino-rest.
-Mike
On 11/11/25 03:14, Vassilis Virvilis wrote:
+1 metoo
I have moved from GWT-RPC to RestyGWT a lifetime ago.I had even contributed to RestyGWT in order to accommodate my use cases.
Later on RestyGWT tried to move from its custom jackson serialization to gwt-jackson. At some point it started providing both options. However I never managed to compile it with gwt-jackson.
Nowadays both RestyGWT and gwt-jackson seem defunct so naturally I am looking for alternatives.
So, me too, I am interested in any war stories you may have. i.e. Does the serialization of complex objects work? Map with Objects, Parametrized Objects, Lists or Collections as keys?
On Tue, Nov 11, 2025 at
9:44 AM 'RobW' via GWT Users <google-web-toolkit@googlegroups.com>
wrote:
Following
with interest. We've discussed moving our server side from
GWT-RPC to Rest many times, but all of the libs have come
up short on us so far. Domino was the one we had left to
look into at some stage when time becomes available.
On Monday, 10
November 2025 at 15:06:40 UTC Michael Conrad wrote:
Hello all, for domino-rest, are formats like {uid0-9+} not supported? Am I doing something else wrong again in my attempt to migrate off of resty-gwt/gwt-jackson? Is this a lost cause and I should just reverse course?
My jakarta jersey rest endpoint is defined as:
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
@Path("/1.0")
public interface UserV1Jakarta {
@Path("/entitlements/modules/{uid0-9+}")
@GET
EntitlementsModulesResponse entitlementsModules(@PathParam("uid") String uid, //
@HeaderParam(HeaderConsts.TOKEN) String token);
//other methods snipped.
}
I am using the following for the gwt side implementation:
// …
import org.dominokit.rest.shared.request.service.annotations.RequestFactory;
@RequestFactory(serviceRoot = ApplicationPaths.API_CONTEXT + ApplicationPaths.BUTTER_USER)
public interface UserV1 extends UserV1Jakarta {
}
I'm calling it as follows:
Console console = DomGlobal.console;
UserV1Factory userV1 = UserV1Factory.INSTANCE;
DominoRestConfig config = DominoRestConfig.getInstance();
console.log("DominoRestConfig initialized");
userV1.entitlementsModules("0", "not-used").onSuccess(m->{
console.log("Got entitlements modules");
m.result.forEach(System.out
);
}).onFailed(e->{
console.log("Failed to get modules");
console.log(e.getHeaders());
console.log(e.getBody());
console.log(e.getStatusText());
console.log(e.getThrowable());
}).send();
And I'm getting in the JS console (superdev mode so I can see any exceptions):
Could not RunAsync request [com.newsrx.butter.client.domino.api.UserV1Factory$UserV1_entitlementsModules@3] ConsoleLogger.java:33:1
Exception: org.dominokit.rest.shared.request.exception.PathParameterMissingException: No parameter provided for path [{uid0-9+}] ConsoleLogger.java:55:1
-Mike
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/e63f7cf1-465f-4880-9500-a57bcc3a57can%40googlegroups.com.
–
Vassilis Virvilis
–
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/CAKbOjEy8djkN9tTOZWEw-7FUNfiqVcvOesJaaHY3%3D4FuwsHCYQ%40mail.gmail.com.
​