The highlights:
- I'm not sure if you get a Jetty server bundled or not if you use the legacy bundled services. The documentation is a little ambiguous to me.
- You do get a stand alone server "dev server" that you can deploy a war to. Great for final testing, but it's unclear if you'll be able to debug on it.
- Your static files worked because the legacy version allows a war file, and you have the maven-war-plugin in your POM.
- If I switch to SpringBoot, I'll move my static files to either a /public or /static directory.
Personally, I'm going to skip the legacy bundled services, and just use the second-generation Java runtime with my own web server.
Cheers!
On Monday 25 December 2023 at 3:48:23 am UTC+11 tim_mac...@yahoo.co.uk wrote:
Looks like Cloud CLI provides a dev server if using the legacy bundled services (App Engine API JAR)?https://cloud.google.com/appengine/migration-center/standard/migrate-to-second-gen/java-differences#framework_flexibilityIf you are using the legacy bundled services, the second-generation Java runtimes provide the Jetty web-serving framework.The Google Cloud CLI for Java includes a local development server for testing your application on your computer. The local development server emulates the App Engine Java runtime environment and all of its services, including Datastore.What do you think ?Re. static files: in my setup appengine:deploy at base directory server project deploys SNAPSHOT.war.Static files in \src\main\webapp end up in its root directory.says in the case of a JAR-file, src/main/webapp has no special meaning and goes on about jar directories that work with Springboot.
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/1d958b8c-9fee-4c7f-9387-cf7aca3a6e22n%40googlegroups.com.
No comments:
Post a Comment