On 16. 05. 2020. 00:23, Dr. Lofi Dewanto wrote:
I would prefer just using:
[...]
(3) Best practice, never mix client- and server-side. Make a stand-alone
Maven project for your client-based webapp / webbrowser.
Could you elaborate this a bit further, please?
IMHO, sharing codebase between client and server, especially domain model
which is really easy to make compatible on both ends, it one of the main
benefits in using GWT. Even further, I'm advising mixed Java/JavaScript
teams to use GWT to export ther domain model as a JS lib to be consumed by
frontend developers which use Angular/React/whatever.
-gkresic.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/589f07dc-558e-de7b-635f-8f6d5a798493%40steatoda.com.
