Short answer: don't start using RequestFactory now, it's been practically unmaintained for years.
Long answer: there's not really a longer answer actually, it's OK to keep using RF in existing projects (if you can't afford moving to something else), but don't start anything with it now. (I wouldn't start anything new with gwt-rpc either BTW, but YMMV) On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote: > I know that GWT Request Factor plays an important role in Java object > persistence and communication between client and server. > However, on the server and client, even one object needs to generate > related classes and interfaces, and then annotation settings etc. need to > be set for each class and interface. > It is complicated and has a lot of trouble to create. > > Originally, these things are like plugins, and it is desirable to select > one object and generate a related class, but do you all know? > > I have been using GWT for over 10 years, but I do not use "RequestFactory" > and operate only with objects like Map by RPC communication. > This can simplify the entire system and greatly reduce the effort required > to create it. > > GWT RequestFactory > https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html > -- 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/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com.
