This project provides an example of an Angular single page application, served by
configured with the
html5 router. Some endpoints have Spring Webflux integration too.
The SinglePageAppConfig makes the magic here.
base-href in configured by the ResourceResolver. It's generated from the value of the application's context-path at runtime when served by tomcat.
It's useful if you want to serve an Angular application with the
html5 router, and avoid the dashed URL.
html5 router mode makes pretty URL, but has a default : Refreshing pages (or accessing them directly) will give you a 404
HTTP error if no RewriteRule is provided by the HTTP server that serves the application.
base-href dynamically can be tricky too. Here it's done once and for all by the ResourceResolver.
If you want to play with the front part, go to the front folder and run
yarn start or
npm start. HTTP requests will be correctly proxyfied to your backend.
The front-end part has been scaffolded with angular-cli.