On Friday, December 2, 2016 at 5:53:46 AM UTC+1, vitrums wrote:
It's also not clear for me why greetingService test classes must've been completely excluded from the modular-webapp archetype.
Because, actually, using <servlet> in GWTTestCases is not seen as a good practice (anymore). GWTTestCases should be unit tests, running in a GWT/browser environment, not integration tests. For that, the preferred way is to use end-to-end tests.
Archetypes in general serve to unify the maximum of core best practices relevant to some particular project structure (tests including), don't they?
Archetypes are meant as scaffolding tools to cut boilerplate down. Putting "too much" things into an archetype means that you have to delete/refactor many things before actually being able to use the generated project.
The gwt-maven-archetypes could include some tests, but the code is so light that it'd be far-fetched and not realistic.
In your specific case, if you want to replicate the test using GreetingService; you'd have to create a new standard JAR module with your server code. The WAR module would depend on it (to include into the WAR/webapp); and the client (gwt-app) module could depend on it with <scope>test</scope>.
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment