In this article we will demonstrate an Angular Front-End app served through Spring Boot's embedded Tomcat. Why do it this way? We can serve an Angular app in different ways (e.g. Apache Web Server, Nginx, etc.). What is so special about serving an Angular app through Spring Boot's Tomcat? There is nothing special. A reason could be that the development team is already well versed in Spring Boot with Tomcat. They have mastered configuring Tomcat and investing in a new web server (e.g. Nginx) is of little value. Another could be the deployment pipeline is already set up to do Java/Maven deployment (e.g. Jenkins). Lastly, it could be that you are a new hire and the development team already do it that way. That is, we don't have a choice but to support an existing Angular FE app served through Spring Boot.
Our focus will be on building the Angular app so that it can be deployed through a Spring Boot fat jar. We will lightly touch on starting a Spring Boot and Angular apps. It is assumed that the reader has knowledge regarding Node, Angular CLI, Java, Maven, Spring Boot, etc. The reader should know how to set up the mentioned technology stack.
Two Ways to Build
As far as I know, there are two ways to build an Angular app so that it can be deployed as single Spring Boot fat jar.
First one is to use the exec-maven-plugin
. This plugin runs the ng build
and the outputPath
of the Angular app must point to src/main/resources/static
so that Angular dist
files are bundled in the jar during packaging.
Second is to use the maven-resources-plugin
. This plugin copies the Angular dist
files to the classes/static
directory of the Spring Boot app. This is the method we will be demonstrating. This way seems to be cleaner because it doesn't populate any files under the Java section of the code. The Angular build code goes straight into the fat jar. This way, all Angular development code and work remain in a separate directory from the Java side of things. And only become one when we build the fat jar. So let's get to it.
Spring Initializr
Head over to Spring Initializr and it should look like below:
Spring Initialzr |
Angular Bit
Under the root directory, create a dev
folder. This is where all the Angular stuff goes. Assuming you have Node, Node Version Manager and Node Package Manager ready, run npm install -g @angular/cli
to install the Angular CLI. Check your installation, ng -v
. We should have something like below:
Angular Version |
Create an Angualr starter app under the dev folder, ng new my-app
. This will create the scaffolding. Change directory to my-app, cd my-app
, then run g serve
. Open localhost:4200, we should have something like below:
My-App on 4200 |
Build the Angular project, ng build
. This will create files in the dist directory. Take note of this folder as we will need it in our POM file. We should see something like below after the build:
Built Files |
These are the built files found in the dist folder.
dist Contents |
Maven Bit
We don't need to change any Java code. The key is in the POM. We will copy the dist files over to the classes/static folder and then Maven (mvn clean package
) will take care of making the fat jar. Add the maven-resources-plugin
like below (make sure you get the diretories right ;) ):
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>copy-resources</id>
<phase>validate</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>${build.directory}/classes/static/</outputDirectory>
<resources>
<resource>
<directory>dev/my-app/dist/my-app</directory>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
Below is the key bit when running mvn clean package
. This tells us the files copied from Angular to Java classes. The number of files should match!
mvn clean package |
Demonstration
Now, run
My-App Served Through Spring Boot's Tomcat |
There you have it. A nice way of serving an Angular app through Spring Boot's fat jar and embedded Tomcat. Grab the full repo here, github.com/jpllosa/angular-fe-spring-boot