On Saturday, May 16, 2020 at 12:44:45 PM UTC+2, Gordan Krešić wrote:
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.
It's not about separating codebases, but separating dependencies/classpaths, to make sure server-side dependencies won't conflict with GWT's own dependencies (e.g. Hibernate Validator, ECJ, Jetty, etc.)
Lofi should probably have said "distinct submodule" rather than "stand-alone project".
See https://github.com/tbroyer/gwt-maven-archetypes (see announcement from 8 years ago: https://blog.ltgt.net/announcing-gwt-maven-archetypes-project/)
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/8a712d00-185e-4559-82ce-05b4d61f52c7%40googlegroups.com.
No comments:
Post a Comment