Gain insights into building scalable applications with Thymeleaf and Spring Boot. Delve into Spring Data, Spring Security, and testing methods to ensure maintainable, portfolio-worthy projects.

maven.tar.gz

13SepBackgroundPostGres

DockerCompose14Sep

OptimizedMvn-22Sep

Moving into root - 24 Sep

From GitHub Repo - 12.4 - 24 Sep

Built from Github and running directly without watcher - 30Sep

Watcher - 29 Sep

From usercode directly - Oct 1

DockerCompose14Sep-Chapter09

OptimizedMvn-22Sep-Chapter11

DockerCompose14Sep-Chapter09-copy

Chapter09-Testing

Cypress

Chapter17-Testing

Cypress-copy

Integration Testing

Initial Chapters

Initial Chapters-copy

Watcher

Initial Chapters-Watcher

Integration Testing-copy

In this course, you will learn how to build easily scalable applications with Thymeleaf and Spring Boot. More specifically, you will combine Thymeleaf and Spring Boot with Spring Data and Spring Security. In a nutshell, this course will give you all the basics you need to start developing an application using Thymeleaf and Spring Boot.

Throughout the course, you will be building an application of a fictional basketball team called Thyme Wizards. Additionally, you will also learn to use unit and integration tests to ensure the proper code functionality and build a maintainable codebase that you can expand upon.

By the end, you will have a new project to add to your portfolio and some great new skills that employers will love.

Building Scalable Applications with Thymeleaf and Spring Boot

## Testing the version

We added a **`version`** field to our **`User`** entity in order to use *Optimistic Locking*. We can quickly test if this works with the following steps:

* Open the application in two different tabs (or browsers).
* Click the “Edit” link for a user in the first tab and do the same (for the same user) in the other tab.
* Change something in the first tab and save.
* Without refreshing the second tab, change something else there and save.


You will get something like this:

# Testing the version

We added a **`version`** field to our **`User`** entity in order to use *Optimistic Locking*. We can quickly test if this works with the following steps:

* Open the application in two different tabs (or browsers).
* Click the “Edit” link for a user in the first tab and do the same (for the same user) in the other tab.
* Change something in the first tab and save.
* Without refreshing the second tab, change something else there and save.


You will get something like this:

Learn how to properly handle Optimistic Locking for the version field in User.

Handling Optimistic Locking Failure

Getting Started

What are Spring Boot and Thymeleaf?

Thymeleaf Introduction

Thyme Wizards

Fragments

Layouts

Controllers

Internationalization

Database Connection

Displaying Data

Forms

Data Editing

Implement Deletion of an Entity

Security

Security - Users from Database

Testing

Testing Using Cypress

Various Tips and Tricks - I

Various Tips and Tricks - II

Conclusion

Appendix

Handling Optimistic Locking Failure

Testing the version