Book Image

Building Applications with Spring 5 and Vue.js 2

By : James J. Ye
Book Image

Building Applications with Spring 5 and Vue.js 2

By: James J. Ye

Overview of this book

Building Applications with Spring 5 and Vue.js 2, with its practical approach, helps you become a full-stack web developer. As well as knowing how to write frontend and backend code, a developer has to tackle all problems encountered in the application development life cycle – starting from the simple idea of an application, to the UI and technical designs, and all the way to implementation, testing, production deployment, and monitoring. With the help of this book, you'll get to grips with Spring 5 and Vue.js 2 as you learn how to develop a web application. From the initial structuring to full deployment, you’ll be guided at every step of developing a web application from scratch with Vue.js 2 and Spring 5. You’ll learn how to create different components of your application as you progress through each chapter, followed by exploring different tools in these frameworks to expedite your development cycle. By the end of this book, you’ll have gained a complete understanding of the key design patterns and best practices that underpin professional full-stack web development.
Table of Contents (23 chapters)
Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Index

Putting two ends together


There are two parts that we need to connect between the frontend and the backend. The first part is the build process. Currently, we need to use mvn and npm to build the two parts separately. Once they are connected, we will only need to execute a single command to build the entire application.

The second part is to bridge the communication between the frontend and the backend. As mentioned, during development, the frontend will be served by webpack-dev-server under a different port than the one of the backend. Currently, both ends use the same port, 8080. We will need to change the port of the frontend to 3000 so that we can have both ends up and running at the same time. When our application is served from http://localhost:3000, the requests that the frontend pages send to the backend at http://localhost:8080, by default, will be blocked by the browser because they are cross-origin. The frontend won't be able to access the response of those requests unless we bridge...