First of all thanks for doing this work. It is hugely appreciated and required in order to avoid GWT and GWT projects look like zombies in a dead landscape.
I am using RestyGWT and yes I also believe it uses Generators (GWT.create() ?). I am facing a problem there since RestyGWT is deadish itself. One of the reasons I abandoned GWT-RPC was Jsinterop. With Jsinterop you can include and link to js libraries in the client. Some of them require data from the backend e.g. datatables.net, d3 etc. GWT-RPC is not compatible with them so I would need to use RequestFactory, which I never liked or another framework. So why have two of them? Use one. Go to JSON. RestyGWT was the only viable choice at the time. With Resty-GWT I can have my POjOs *without annotations*, and I can share them between backend, frontend and other clients (non web). RestyGWT has 2 backends: - an older private jackson like (forked) implementation. That's the one I use. - a newer gwt-jackson based one. This one never worked for me. Furthermore I have invested in RestGWT and I have some custom patches so RestyGWT can transmit my generics. At this point domino-jackson and domino-rest looks like the way forward but from a quick look require annotations in the POJO and this is something that I would like to avoid. Just my 2 bits. Sorry if incoherent... On Wed, Jan 10, 2024 at 9:45 PM Michael Conrad <mich...@newsrx.com> wrote: > You should investigate the DominoKit project. They have a much more > up-to-date JSON/Jackson-ish implementation. > > Ref: https://github.com/DominoKit/domino-rest > > > > On 1/10/24 11:26, Christian Hebert wrote: > > Hi guys, I've seen the changes in the new release regarding jakarta > servlets, which is great, it's a step toward jakarta but to this day, GWT > is still based on the Servlet API 3.1. > > Prior of seeing that change, I tried to move away from RPC calls and use > http requests instead. I found a nice library called RestyGWT ( > https://resty-gwt.github.io/) who can really simplify the process of > handling json data from/to a Rest API. > > So I converted my GWT remote servlets to a Rest API, made a few minor > changes in my client code and voilà, I was able to deploy it on a Jakarta > Application server since there is no GWT involved on the server side > anymore. > > The last version of RestyGWT has been release in 2020 so I'm not sure how > active this project is but from what I've seen it's enough for me. > > So, I would like to get your thoughts on that. Would you go on that road? > stick to RPC calls and wait for a version of GWT based on Jakarta? build > your "own" GWT with the changes introduced in the vew version? > -- > 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/8fa7dc19-2a15-442d-93b2-adebb947046cn%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit/8fa7dc19-2a15-442d-93b2-adebb947046cn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > 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/156e77ff-25bd-4743-8798-0d0347d1866d%40newsrx.com > <https://groups.google.com/d/msgid/google-web-toolkit/156e77ff-25bd-4743-8798-0d0347d1866d%40newsrx.com?utm_medium=email&utm_source=footer> > . > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAKbOjEy6q14UbmhrQYj-4CrTD6QjFwuygPxM757DjD4%3DkRs1dg%40mail.gmail.com.
