application.properties structure in Spring Boot - Step-by-Step Execution

Concept Flow - application.properties structure

Start: Load application.properties

↓

Read each property line

↓

Parse key=value pair

↓

Store in Environment

↓

Use properties in app components

↓

End

Spring Boot reads the application.properties file line by line, parses each key=value pair, stores them in the environment, and makes them available to the application.

Execution Sample

Spring Boot

server.port=8080
spring.datasource.url=jdbc:mysql://localhost:3306/db
logging.level.org.springframework=DEBUG

Defines server port, database URL, and logging level in application.properties.

Execution Table

Step	Line Read	Parsed Key	Parsed Value	Environment Update
1	server.port=8080	server.port	8080	server.port=8080
2	spring.datasource.url=jdbc:mysql://localhost:3306/db	spring.datasource.url	jdbc:mysql://localhost:3306/db	spring.datasource.url=jdbc:mysql://localhost:3306/db
3	logging.level.org.springframework=DEBUG	logging.level.org.springframework	DEBUG	logging.level.org.springframework=DEBUG
4	EOF	-	-	All properties loaded

💡 End of file reached, all properties parsed and stored

Variable Tracker

Environment	Start	After 1	After 2	After 3	Final
Properties Map	{}	{server.port=8080}	{server.port=8080, spring.datasource.url=jdbc:mysql://localhost:3306/db}	{server.port=8080, spring.datasource.url=jdbc:mysql://localhost:3306/db, logging.level.org.springframework=DEBUG}	{server.port=8080, spring.datasource.url=jdbc:mysql://localhost:3306/db, logging.level.org.springframework=DEBUG}

Key Moments - 3 Insights

Why does each line need to be in key=value format?

Because Spring Boot parses each line as a key=value pair to store in the environment, as shown in execution_table rows 1-3.

What happens if a line is empty or a comment?

Spring Boot ignores empty lines and lines starting with # or !, so they do not appear in the environment or execution_table.

Can properties override each other?

Yes, if the same key appears multiple times, the last one wins and updates the environment accordingly.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'spring.datasource.url' after step 2?

A DEBUG

B 8080

C jdbc:mysql://localhost:3306/db

D Not set yet

💡 Hint

Check the 'Parsed Value' column at step 2 in execution_table

At which step does the environment contain the logging level property?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Environment Update' column and see when 'logging.level.org.springframework' appears

If a new line 'server.port=9090' is added after step 3, what happens to the environment?

A server.port remains 8080

B server.port changes to 9090

C A new property server.port2=9090 is added

D An error occurs

💡 Hint

Properties override previous values if keys are the same, as explained in key_moments

Concept Snapshot

application.properties is a simple text file with key=value lines.
Spring Boot reads it line by line, parsing keys and values.
Properties are stored in the environment for app use.
Empty lines and comments are ignored.
Later properties override earlier ones if keys repeat.

Full Transcript

Spring Boot starts by loading the application.properties file. It reads each line, expecting a key=value format. Each key and value is parsed and stored in the environment map. This environment is then used by the application to configure settings like server port, database connection, and logging levels. Empty lines or comments starting with # or ! are skipped. If the same key appears multiple times, the last value is used. This process ensures the app has all configuration values ready before it runs.

Practice

1. What is the primary purpose of the application.properties file in a Spring Boot project?

easy

A. To store configuration settings as key=value pairs

B. To write Java code for the application

C. To define database tables

D. To create HTML templates

Solution

1. Step 1: Understand the role of application.properties

   This file is used to hold configuration settings for the Spring Boot app.

2. Step 2: Identify the format and purpose

   It stores settings as simple key=value pairs to configure app behavior without code changes.

3. Final Answer:

   To store configuration settings as key=value pairs -> Option A

4. Quick Check:

   Config file = key=value pairs [OK]

Hint: Remember: properties file = settings in key=value form [OK]

Common Mistakes:

• Confusing properties file with source code files
• Thinking it stores HTML or database schema
• Assuming it runs application logic

2. Which of the following is the canonical syntax to set the server port to 8081 in application.properties?

easy

A. server-port=8081

B. server_port=8081

C. server.port=8081

D. serverPort=8081

Solution

1. Step 1: Recall the key naming convention

   Spring Boot uses dot notation to group related settings, so keys use dots, not dashes or underscores.

2. Step 2: Match the correct syntax

   The correct key for server port is server.port, followed by = and the port number.

3. Final Answer:

   server.port=8081 -> Option C

4. Quick Check:

   Dots separate groups in keys = correct syntax [OK]

Hint: Use dots, not dashes or underscores in keys [OK]

Common Mistakes:

• Using dashes instead of dots in keys
• Using underscores or camelCase instead of dots
• Missing the equal sign

3. Given this application.properties snippet:

spring.datasource.url=jdbc:mysql://localhost:3306/mydb
spring.datasource.username=root
spring.datasource.password=pass123

What will Spring Boot use for the database username?

medium

A. root

B. localhost

C. pass123

D. mydb

Solution

1. Step 1: Identify the key for username

   The key spring.datasource.username holds the database username.

2. Step 2: Read the value assigned

   The value assigned is root, so Spring Boot uses this as the username.

3. Final Answer:

   root -> Option A

4. Quick Check:

   Username key value = root [OK]

Hint: Look for .username key to find DB user [OK]

Common Mistakes:

• Confusing URL or password as username
• Reading the database name as username
• Ignoring the key names

4. Identify the error in this application.properties snippet:

server.port: 9090
spring.application.name=MyApp

medium

A. Key names should be uppercase

B. No error, syntax is correct

C. Using colon instead of equal sign for server.port

D. Missing quotes around MyApp

Solution

1. Step 1: Check key-value separator

   In application.properties, both equal sign (=) and colon (:) are valid separators, as per Java Properties format.

2. Step 2: Verify other syntax rules

   Keys use lowercase with dots, quotes optional for simple values like 'MyApp' and numbers.

3. Final Answer:

   No error, syntax is correct -> Option B

4. Quick Check:

   = and : both valid [OK]

Hint: Properties support =, :, or space as separators [OK]

Common Mistakes:

• Thinking colon (:) is invalid separator
• Thinking quotes are mandatory for strings
• Assuming uppercase keys are required

5. You want to configure a nested property for mail settings in application.properties like this:

mail.host=smtp.example.com
mail.port=587
mail.credentials.username=user1
mail.credentials.password=secret

Which statement about this structure is correct?

hard

A. Properties cannot be nested; each key must be unique without dots

B. Nested properties require JSON format, so this is invalid

C. Underscores should be used instead of dots for nesting

D. Dots group related settings, so mail.credentials.username is nested under mail > credentials

Solution

1. Step 1: Understand dot notation in properties

   Dots in keys group related settings hierarchically, like folders in a file system.

2. Step 2: Analyze the example keys

   Keys like mail.credentials.username mean username is inside credentials, which is inside mail.

3. Final Answer:

   Dots group related settings, so mail.credentials.username is nested under mail > credentials -> Option D

4. Quick Check:

   Dots = nested groups in properties [OK]

Hint: Dots create groups, like folders in settings [OK]

Common Mistakes:

• Thinking JSON is needed for nesting
• Using underscores instead of dots
• Believing nesting is not allowed