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

We just introduced the Thymeleaf expressions (enclosed within `th:*` tags). These can be classified into six categories:

1. Variables
2. Text
3. Selected objects
4. Links
5. Literal substitutions
6. Expression inlining




Thymeleaf expressions in the simple HTML are **[OGNL](http://commons.apache.org/proper/commons-ognl/language-guide.html)** (Object-Graph Navigation Language) expressions by default. However, the expressions in a Spring Boot application are **[SpringEL](https://docs.spring.io/spring-webflow/docs/current/reference/html/el.html)** (Spring Expression Language). Luckily, the syntax is mostly the same in both cases.

# Variables

When a Thymeleaf template gets processed, the application will put variables in the context via the
controller. We can reference those variables in the templates via the `${…}` syntax. For example:

``` html
<div th:text="${username}"></div>
```

Suppose there is a `String` in the Thymeleaf context with the name `username` that has the value "John Doe." The HTML will be rendered as:

``` html
<div>John Doe</div>
```

>The variable in the context does not need to be a `String`. Other types will have their `toString()`
method invoked.

## Methods

We can also call methods. For example:

``` html
<div th:text="${user.getName()}"></div>
```

## Properties

Similarly, if the method name adheres to the #key# JavaBeans specification: JavaBeans specification describes JavaBeans since they were introduced in JDK #key#,  we can simulate property access like:

``` html
<div th:text="${user.name}"></div>
```

## Map
If the object in the context is a map, then dot notation can be used to access a value via its key:

``` html
<div th:text="${capitalsOfTheWorld.Belgium}"></div>
```

Alternatively, we can use the bracket syntax. For certain keys (for example, if they contain spaces) we will need to use the bracket syntax:

``` html
<div th:text="${capitalsOfTheWorld['The Netherlands']}"></div>
```

## Array or list

Collections allowing indexed access can be used like:

``` html
<div th:text="${vehiclesList[0].name}"></div>
```

## Text

Most applications need to be translated into the language of the user. Even if it is not a requirement at the start, we will probably want to do this in case it ever becomes a requirement. Its syntax is:

``` html
<h2 th:text="#{dashboard.title}"></h2>
```

By default, Spring Boot will pick up translations from a
`src/main/resources/messages.properties` file:

```
dashboard.title=Dashboard
```

We can add additional languages by adding another such file but postfixing the file name with the
locale. For example, use `messages_nl.properties` for Dutch translations.

## Selected objects

Thymeleaf has a kind of shortcut syntax if we need to use many properties of a single object.
Suppose we have a template that displays information about a car like this:

# Variables

When a Thymeleaf template gets processed, the application will put variables in the context via the
controller. We can reference those variables in the templates via the `＄{…}` syntax. For example:

``` html
<div th:text="${username}"></div>
```

Suppose there is a `String` in the Thymeleaf context with the name `username` that has the value "John Doe." The HTML will be rendered as:

``` html
<div>John Doe</div>
```

>The variable in the context does not need to be a `String`. Other types will have their `toString()`
method invoked.

## Methods

We can also call methods. For example:

``` html
<div th:text="${user.getName()}"></div>
```

## Properties

Similarly, if the method name adheres to the #key# JavaBeans specification: JavaBeans specification describes JavaBeans since they were introduced in JDK #key#,  we can simulate property access like:

``` html
<div th:text="${user.name}"></div>
```

## Map
If the object in the context is a map, then dot notation can be used to access a value via its key:

``` html
<div th:text="${capitalsOfTheWorld.Belgium}"></div>
```

Alternatively, we can use the bracket syntax. For certain keys (for example, if they contain spaces) we will need to use the bracket syntax:

``` html
<div th:text="${capitalsOfTheWorld['The Netherlands']}"></div>
```

## Array or list

Collections allowing indexed access can be used like:

``` html
<div th:text="${vehiclesList[0].name}"></div>
```

## Text

Most applications need to be translated into the language of the user. Even if it is not a requirement at the start, we will probably want to do this in case it ever becomes a requirement. Its syntax is:

``` html
<h2 th:text="#{dashboard.title}"></h2>
```

By default, Spring Boot will pick up translations from a
`src/main/resources/messages.properties` file:

```
dashboard.title=Dashboard
```

We can add additional languages by adding another such file but postfixing the file name with the
locale. For example, use `messages_nl.properties` for Dutch translations.

## Selected objects

Thymeleaf has a kind of shortcut syntax if we need to use many properties of a single object.
Suppose we have a template that displays information about a car like this:

Get introduced to the usage of Thymeleaf expressions.

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

Thymeleaf Expressions

Variables