+1 nats.io
On Fri, Jan 12, 2024 at 10:33 AM Jens wrote:
> If you do not have special needs I think GWT-RPC is still fine especially
> with a jakarta version now available. But while it is easy to use it also
> has some annoying downsides you have to live with.
>
> However there are quite some
If you do not have special needs I think GWT-RPC is still fine especially
with a jakarta version now available. But while it is easy to use it also
has some annoying downsides you have to live with.
However there are quite some options:
- JsInterop based DTOs + JSON.parse/stringify. However you
There may have been some Chrome updates in the last few months;
occasionally, I must hard refresh to get the latest code from nocache.js.
(That did not happen in years past)
Anyway, I always check in Developer Tools in Chrome to make sure there are
no errors in the "Console" and all the
Fully agree - and very much like the example!
Leon Pennings schrieb am Fr. 12. Jan. 2024 um
14:59:
> I think moving away from gwt-rpc is a bad idea.
> A big advantage of GWT is that I can code everything in java and do not
> have to serialize anything to and from text.
> That to me is one of
I think moving away from gwt-rpc is a bad idea.
A big advantage of GWT is that I can code everything in java and do not
have to serialize anything to and from text.
That to me is one of the usp's of GWT.
Going from java -> json -> java (or gwt java), is like trying to have a
complex
