You are currently viewing Configuring Properties in Spring Boot with @Value:

Configuring Properties in Spring Boot with @Value:

In Spring Boot, the @Value annotation provides a simple way to inject values from application properties directly into your beans. This tutorial will guide you through using @Value with examples to access and use configuration properties in a Spring Boot application.


Ensure you have the following set up:

  • A Spring Boot project (you can use the Spring Initializer to generate one).
  • An integrated development environment (IDE) of your choice.

Step 1: Add Dependencies

Make sure your pom.xml (if using Maven) or build.gradle (if using Gradle) includes the necessary dependencies for Spring Boot.


Step 2: Use @Value in Your Beans

Let’s say you have a simple Spring bean that requires a configuration property. You can use @Value to inject this property directly.

In this example, the @Value("${app.greeting}") annotation injects the value of the app.greeting property into the greeting field.

Step 3: Define Properties in

Now, define the properties you want to inject in your file.

Step 4: Inject the Bean and Use the Value

Inject the MyBean into your components or controllers where you need access to the configured properties.

Step 5: Run Your Application

Run your Spring Boot application and navigate to http://localhost:8080/greet. You should see the greeting message printed in the console.

Additional @Value Examples

Injecting Multiple Values

Using Default Values

In this example, if app.greeting is not found in the properties, the default value “Default Greeting” will be used.


The @Value annotation in Spring Boot provides a straightforward way to inject configuration properties into your beans. It allows you to externalize configuration and make your application more flexible. While it’s suitable for simple scenarios, for more complex cases involving multiple properties or nested structures, you might consider using @ConfigurationProperties. Choose the approach that best fits your specific use case and project requirements.

Leave a Reply