Re: Is moving away from RPC a good idea?

[Vassilis Virvilis]

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  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
> 
> .
>
>
> --
> 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
> 
> .
>


-- 
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.

Re: Announcing GWT 2.10.1 and 2.11 releases

[am...@mun.co.il]

Thank you!

On Tuesday, January 9, 2024 at 11:36:08 PM UTC+2 Colin Alworth wrote:

> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
> second release under the new groupId, be sure when you update to change 
> away from "com.google.gwt", as it will not get more updates.
>
> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
> vulnerable projects are aware of any problem, compile warnings will be 
> emitted if a problem is detected, and the server will default to not 
> allowing any vulnerable RemoteService instances. See 
> https://github.com/gwtproject/gwt/issues/9709 for information on the 
> issue, how we're responding to it, and how any additional follow-up might 
> look.
>
> Other highlights:
>
>- Transitioned to GitHub pull requests for new contributions, with 
>nightly builds running on GitHub Actions.
>- Added release artifacts for jakarta.servlet packages for both 
>RequestFactory and GWT-RPC.
>- Tested support for running on Java 21. This is likely to be the 
>final minor release series to support running on Java 8.
>- Updated JRE emulation to support Java 11 for Collections, streams, 
>and more.
>
> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
> complete release notes.
>
> This release wouldn't have been possible without help from so many 
> contributors, including developers, testers, and sponsors. A short list of 
> the teams and individuals that directly brought us this release: Juan Pablo 
> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
> Insurance Insight Inc. Join us on the issue tracker 
>  or at our OpenCollective page 
>  to help make future releases 
> possible.
>

-- 
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/140ebe0b-c616-4338-b150-b95a6489389dn%40googlegroups.com.

The GWT application hangs on the loading screen

[Antonio Capone]

Hi all. I deployed an app using GWT on Cloud. It's deployed and working, 
but when you log in, the browser window just says "Loading" and seems to 
hang indefinitely. Works fine locally in Eclipse.
Has this ever happened to you? Is there anyone who can help me understand 
why this happens?
Many 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/669136be-ee5f-48ea-82ac-c18436a75bb4n%40googlegroups.com.

Re: Is moving away from RPC a good idea?

['Frank Hossfeld' via GWT Users]

Using domino-rest, the POJO have usually only one annotation: @JSONMapper.

Vassilis Virvilis schrieb am Donnerstag, 11. Januar 2024 um 09:35:05 UTC+1:

> 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  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-tool...@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
>>  
>> 
>> .
>>
>>
>> -- 
>> 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-tool...@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
>>  
>> 
>> .
>>
>
>
> -- 
> 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/1f442a59-8e19-427e-84c1-9a3914cfe08bn%40googlegroups.com.

Re: The GWT application hangs on the loading screen

['Frank Hossfeld' via GWT Users]

Check if the nochache.js gets loaded at a applicaiton staert or if it got a 
404. In this case something with the URI is not ok.

Antonio Capone schrieb am Donnerstag, 11. Januar 2024 um 10:56:55 UTC+1:

> Hi all. I deployed an app using GWT on Cloud. It's deployed and working, 
> but when you log in, the browser window just says "Loading" and seems to 
> hang indefinitely. Works fine locally in Eclipse.
> Has this ever happened to you? Is there anyone who can help me understand 
> why this happens?
> Many 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/561f301d-8bd9-4a99-8b10-93c2cf2cc3d3n%40googlegroups.com.

Re: Announcing GWT 2.10.1 and 2.11 releases

[lofid...@gmail.com]

Great work GWT Team!

Thanks a lot!

Lofi

am...@mun.co.il schrieb am Donnerstag, 11. Januar 2024 um 10:56:43 UTC+1:

> Thank you!
>
> On Tuesday, January 9, 2024 at 11:36:08 PM UTC+2 Colin Alworth wrote:
>
>> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
>> second release under the new groupId, be sure when you update to change 
>> away from "com.google.gwt", as it will not get more updates.
>>
>> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
>> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
>> vulnerable projects are aware of any problem, compile warnings will be 
>> emitted if a problem is detected, and the server will default to not 
>> allowing any vulnerable RemoteService instances. See 
>> https://github.com/gwtproject/gwt/issues/9709 for information on the 
>> issue, how we're responding to it, and how any additional follow-up might 
>> look.
>>
>> Other highlights:
>>
>>- Transitioned to GitHub pull requests for new contributions, with 
>>nightly builds running on GitHub Actions.
>>- Added release artifacts for jakarta.servlet packages for both 
>>RequestFactory and GWT-RPC.
>>- Tested support for running on Java 21. This is likely to be the 
>>final minor release series to support running on Java 8.
>>- Updated JRE emulation to support Java 11 for Collections, streams, 
>>and more.
>>
>> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
>> complete release notes.
>>
>> This release wouldn't have been possible without help from so many 
>> contributors, including developers, testers, and sponsors. A short list of 
>> the teams and individuals that directly brought us this release: Juan Pablo 
>> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
>> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
>> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
>> Insurance Insight Inc. Join us on the issue tracker 
>>  or at our OpenCollective page 
>>  to help make future releases 
>> possible.
>>
>

-- 
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/b4afb9d3-a3eb-40a5-98db-59d950ba0742n%40googlegroups.com.

Re: Announcing GWT 2.10.1 and 2.11 releases

[Filipe Sousa]

👍

On Tuesday, January 9, 2024 at 9:36:08 PM UTC Colin Alworth wrote:

> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
> second release under the new groupId, be sure when you update to change 
> away from "com.google.gwt", as it will not get more updates.
>
> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
> vulnerable projects are aware of any problem, compile warnings will be 
> emitted if a problem is detected, and the server will default to not 
> allowing any vulnerable RemoteService instances. See 
> https://github.com/gwtproject/gwt/issues/9709 for information on the 
> issue, how we're responding to it, and how any additional follow-up might 
> look.
>
> Other highlights:
>
>- Transitioned to GitHub pull requests for new contributions, with 
>nightly builds running on GitHub Actions.
>- Added release artifacts for jakarta.servlet packages for both 
>RequestFactory and GWT-RPC.
>- Tested support for running on Java 21. This is likely to be the 
>final minor release series to support running on Java 8.
>- Updated JRE emulation to support Java 11 for Collections, streams, 
>and more.
>
> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
> complete release notes.
>
> This release wouldn't have been possible without help from so many 
> contributors, including developers, testers, and sponsors. A short list of 
> the teams and individuals that directly brought us this release: Juan Pablo 
> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
> Insurance Insight Inc. Join us on the issue tracker 
>  or at our OpenCollective page 
>  to help make future releases 
> possible.
>

-- 
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/c9cca5aa-7a43-4224-9909-baf760eb5190n%40googlegroups.com.

Re: Is moving away from RPC a good idea?

[Vegegoku]

Domino-rest is up-to-date well documented and in our next release 
-Currently available in the HEAD-SNAPSHOT- we are moving to jakarta 
namespace.

Full documentation can be found in our website 
here https://dominokit.com/solutions/domino-rest/v1/docs/getting-started

On Wednesday, January 10, 2024 at 7:26:04 PM UTC+3 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/b203501d-6b3c-4c77-ab6a-549be840a429n%40googlegroups.com.

Re: Is moving away from RPC a good idea?

[Vegegoku]

The annotation on the POJO is not required at all, Domino-rest will auto 
generate the json-mapping classes if the jax-rs/jakarata resource 
consumes/produces a json even if the annotation is missing, so you can keep 
the POJO clean or only have Jackson compatible annotations. ;-)

On Thursday, January 11, 2024 at 11:35:05 AM UTC+3 Vassilis Virvilis wrote:

> 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  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-tool...@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
>>  
>> 
>> .
>>
>>
>> -- 
>> 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-tool...@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
>>  
>> 
>> .
>>
>
>
> -- 
> 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/4fc34b98-5504-4981-a942-ae633f4b77e9n%40googlegroups.com.

Re: Is moving away from RPC a good idea?

[Vassilis Virvilis]

Hi Vegegoku,

Thanks for clearing that up.

At some point I will definitely try the domino-rest/jackson.

For now I dread the time I will eventually be forced to port my current
setup.


On Thu, Jan 11, 2024 at 5:13 PM Vegegoku  wrote:

> The annotation on the POJO is not required at all, Domino-rest will auto
> generate the json-mapping classes if the jax-rs/jakarata resource
> consumes/produces a json even if the annotation is missing, so you can keep
> the POJO clean or only have Jackson compatible annotations. ;-)
>
> On Thursday, January 11, 2024 at 11:35:05 AM UTC+3 Vassilis Virvilis wrote:
>
>> 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  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-tool...@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
>>> 
>>> .
>>>
>>>
>>> --
>>> 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-tool...@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
>>> 
>>> .
>>>
>>
>>
>> --
>> 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/4fc34b98-5504-4981-a942-ae633f4b77e9n%40googlegroups.com
>