Why Custom configuration properties in Spring Boot? - Purpose & Use Cases

The Big Idea

Discover how to tame your app's settings chaos with one simple pattern!

The Scenario

Imagine you have many settings scattered across your Spring Boot app, and you need to change them often.

You edit multiple files and hunt for values everywhere.

The Problem

Manually managing configuration is confusing and error-prone.

You might forget to update a value or mix up formats, causing bugs.

It's hard to keep track and test changes safely.

The Solution

Custom configuration properties let you group related settings into neat classes.

Spring Boot automatically loads and validates them from your config files.

This keeps your code clean and your settings easy to manage.

Before vs After

✗ Before

String dbUrl = env.getProperty("db.url");
String dbUser = env.getProperty("db.user");

✓ After

@ConfigurationProperties(prefix = "db")
@Component
class DbProperties {
  public String url;
  public String user;
}

What It Enables

You can organize and validate all your app settings in one place, making changes safe and simple.

Real Life Example

Think of a web app where you configure database, email, and security settings separately but want them all easy to find and update.

Key Takeaways

Manual config is scattered and risky.

Custom properties group settings logically.

Spring Boot loads and validates them automatically.

Practice

1. What is the main purpose of using @ConfigurationProperties in Spring Boot?

easy

A. To create REST endpoints automatically

B. To enable security features in the application

C. To define database connection pools

D. To bind external configuration properties to a Java class

Solution

1. Step 1: Understand the role of @ConfigurationProperties

   This annotation is used to map external configuration values (from files like application.properties or application.yml) to fields in a Java class.

2. Step 2: Compare with other options

   Options A, C, and D relate to other Spring Boot features but not to property binding.

3. Final Answer:

   To bind external configuration properties to a Java class -> Option D

4. Quick Check:

   Property binding = B [OK]

Hint: Remember: @ConfigurationProperties binds config files to classes [OK]

Common Mistakes:

• Confusing @ConfigurationProperties with @RestController
• Thinking it manages database connections
• Assuming it enables security automatically

2. Which of the following is the correct way to enable @ConfigurationProperties support in a Spring Boot application?

easy

A. Add @SpringBootApplication on the properties class

B. Add @EnableConfigurationProperties on a configuration class or main class

C. Add @RestController on the properties class

D. Add @ComponentScan on the properties class

Solution

1. Step 1: Identify how to activate configuration properties

   Spring Boot requires @EnableConfigurationProperties on a configuration or main class to enable binding of @ConfigurationProperties classes.

2. Step 2: Review other annotations

   @ComponentScan scans components but does not enable properties binding. @RestController is for web controllers. @SpringBootApplication is for main app class but does not alone enable properties binding.

3. Final Answer:

   Add @EnableConfigurationProperties on a configuration class or main class -> Option B

4. Quick Check:

   Enable config properties = D [OK]

Hint: Use @EnableConfigurationProperties to activate property binding [OK]

Common Mistakes:

• Confusing @ComponentScan with enabling properties
• Adding @RestController on properties class
• Assuming @SpringBootApplication alone enables properties

3. Given the following properties in application.yml and class, what will be the output of System.out.println(appProperties.getTimeout())?

application.yml:
app:
  timeout: 5000

Java class:
@ConfigurationProperties(prefix = "app")
public class AppProperties {
    private int timeout;
    public int getTimeout() { return timeout; }
    public void setTimeout(int timeout) { this.timeout = timeout; }
}

medium

A. null

B. 0

C. 5000

D. Compilation error

Solution

1. Step 1: Understand property binding from YAML to class

   The app.timeout property in YAML is set to 5000. The class with @ConfigurationProperties(prefix = "app") binds this value to the timeout field.

2. Step 2: Check getter method output

   Calling getTimeout() returns the bound value 5000, so the printed output is 5000.

3. Final Answer:

   5000 -> Option C

4. Quick Check:

   Bound value printed = 5000 [OK]

Hint: Property prefix matches class prefix to bind values correctly [OK]

Common Mistakes:

• Forgetting to add setter method causes binding failure
• Using wrong prefix in annotation
• Expecting null or default instead of bound value

4. Identify the error in this custom properties class that prevents property binding:

@ConfigurationProperties(prefix = "server")
public class ServerProperties {
    private String port;
    public String getPort() { return port; }
    // Missing setter method
}

medium

A. Missing setter method for 'port' prevents binding

B. Prefix 'server' is invalid and causes error

C. Class must be annotated with @Component

D. Field 'port' should be public for binding

Solution

1. Step 1: Check property binding requirements

   Spring Boot binds properties using setters. Without a setter for 'port', the value cannot be set.

2. Step 2: Validate other options

   The prefix 'server' is valid. The class does not require @Component if registered via @EnableConfigurationProperties. Fields should be private with getters/setters, not public.

3. Final Answer:

   Missing setter method for 'port' prevents binding -> Option A

4. Quick Check:

   Setter missing = binding fails [OK]

Hint: Always add setters for fields to enable binding [OK]

Common Mistakes:

• Assuming prefix must be custom or different
• Thinking @Component is always required
• Making fields public instead of using setters

5. You want to create a nested configuration property for a mail server with host and port inside application.properties like this:

mail.server.host=smtp.example.com
mail.server.port=587

Which of the following Java classes correctly models this nested property using @ConfigurationProperties?

hard

A. @ConfigurationProperties(prefix = "mail")
public class MailProperties {
private Server server;
public static class Server {
private String host;
private int port;
// getters and setters
}
// getters and setters for server
}

B. @ConfigurationProperties(prefix = "mail.server")
public class MailProperties {
private String host;
private int port;
// getters and setters
}

C. @ConfigurationProperties(prefix = "mail")
public class MailProperties {
private String host;
private int port;
// getters and setters
}

D. @ConfigurationProperties(prefix = "mail.server")
public class MailProperties {
private Server server;
public static class Server {
private String host;
private int port;
// getters and setters
}
// getters and setters for server
}

Solution

1. Step 1: Understand nested property binding

   Properties like mail.server.host require a class with prefix mail and a nested class Server to hold host and port.

2. Step 2: Analyze options

   @ConfigurationProperties(prefix = "mail") public class MailProperties { private Server server; public static class Server { private String host; private int port; // getters and setters } // getters and setters for server } correctly uses @ConfigurationProperties(prefix = "mail") with a nested Server class. @ConfigurationProperties(prefix = "mail.server") public class MailProperties { private String host; private int port; // getters and setters } flattens properties incorrectly. @ConfigurationProperties(prefix = "mail") public class MailProperties { private String host; private int port; // getters and setters } misses nesting. @ConfigurationProperties(prefix = "mail.server") public class MailProperties { private Server server; public static class Server { private String host; private int port; // getters and setters } // getters and setters for server } uses prefix mail.server but still nests, which is inconsistent.

3. Final Answer:

   @ConfigurationProperties(prefix="mail") with nested Server class -> Option A

4. Quick Check:

   Nested class with prefix mail = A [OK]

Hint: Use nested classes for nested property groups [OK]

Common Mistakes:

• Using wrong prefix for nested properties
• Flattening nested properties into one class
• Missing getters/setters in nested class