Spring Boot Annotations

[thrive_toggles_group”][thrive_toggles title=”Read other articles of this series :” no=”1/1″]


In this post, we will explore the Spring Boot annotations. We will discuss the basic Spring Boot annotations.


Spring Boot annotations

Spring Boot comes with the auto-configuration feature which makes building it easier to build Spring based enterprise application. Let’s cover some of the most important annotation available in the Spring Boot framework.


1. @SpringBootApplication

This is one of the most important and core annotation from Spring Boot. We use this annotation to mark the main class of our Spring Boot application.

public class SpringOrderAnnotationApplication {

 public static void main(String[] args) {
  SpringApplication.run(SpringOrderAnnotationApplication.class, args);

@SpringBootApplication is a convenience annotation that is equal to declaring @Configuration, @EnableAutoConfigurationand @ComponentScan with their default attributes.

You have the option to use @Configuration, @EnableAutoConfiguration, and @ComponentScan individually but the recommendation is to @SpringBootApplication annotation.


2. @EnableAutoConfiguration

@EnableAutoConfiguration annotation is the intelligent configuration system available with Spring Boot. As the name suggests, Spring Boot system attempting to guess and configure beans that you are likely to need. Auto-configuration classes are usually applied based on your classpath and what beans you have defined.

Auto-configuration is intelligent and will back-away as you define more of your own configuration. 

package com.javadevjournal;

import org.springframework.context.annotation.Configuration;

public class CarConfig {}

Read Spring Boot Auto Configuration for auto configurations features.


3. @Condition Annotations

Spring Boot provides the option to create custom auto-configurations. While writing these custom auto-configuration, we want Spring to use them conditionally. To handle this, we may want to include one or more @Conditional annotations on our auto-configuration class. In this section, we will discuss some of these@Conditional annotations.


3.1 @ConditionalOnClass and @ConditionalOnMissingClass

These annotations are also known as class conditions. These annotations allow configurations based on the presence or absence of specific classes. Let’s take a look at the following example to understand these conditions more clearly.

class MySQLAutoConfiguration {

In the above example, if DataSource class is present in the classpath, this condition is matching and Spring Boot will load the configuration available in the MySQLAutoConfiguration class.

@ConditionalOnMissingClass works similar to @ConditionalOnClass.


3.2 @ConditionalOnBean and @ConditionalOnMissingBean

These annotations are also known as bean conditions and let a bean inclusion based on the presence or absence of specific beans.

public class CarConfig {

 public CarService carService() {

In the preceding example, Spring creates the carService bean if bean of type CarService is already in the ApplicationContext. @ConditionOnMissingBean works in a similar way but in reverse condition.


3.3 @ConditionalOnProperty

The @ConditionalOnProperty annotation lets configuration be included based on a Spring Environment property. Use the prefix and name attributes to specify the property for checking. Let’s take an example to understand it in more detail.

@ConditionalOnProperty(prefix = "spring.rabbitmq", name = "dynamic")
public AmqpAdmin amqpAdmin(CachingConnectionFactory connectionFactory) {
 return new RabbitAdmin(connectionFactory);

In the above configuration, the condition matches if spring.rabbitmq.dynamic is present in the Environment.


3.4 @ConditionalOnResource Annotation

The @ConditionalOnResource annotation lets configuration be included only when a specific resource is present. Let’s create an example to understand it more clearly.

@ConditionalOnResource(resources = "classpath:mysql.properties")
Properties databaseProperties() {
 // ...

In the above example, we are adding extra database properties if mysql.properties file is available in the classpath.

@ConditionalOnResource(resources = "classpath:META-INF/build-info.properties")
Properties buildProperties() {
 // ...


3.5 @ConditionalOnWebApplication and @ConditionalOnNotWebApplication

These annotations let configuration be included depending on whether the application is a “web application”.Let’s take an example where we want to expose a service for a web application, to handle this use case, we use @ConditionalOnWebApplication annotation.

Version applicationVersion() { // .. }


3.6 @ConditionalOnExpression Annotation

The @ConditionalOnExpression annotation allows configurations based on the result of a SpEL expression. Spring will use the marked definition when the SpEL expression evaluated to true

  public class WebController { // ... }

Let’s take a look at another example, where we want to include certain configurations for development mode only

DataSource dataSource() {
    // ...


3.7 @Conditional

Most of the auto-configuration feature of Spring Boot is building based on @Conditional annotation. Spring 4.0 introduced the @Conditional annotation. This annotation indicates that a component is only eligible for registration when all specified conditions match. We can use this annotation to build our own custom conditions not available in the Spring Boot annotation defined in this post.

To get a basic understanding, Let’s say we want to create a service which recommends an insurance to the customer based on the domestic or international travel.

public interface Insurance {
 RecommendedPolicy insurance();

public class DomesticInsurance implements Insurance {

 public RecommendedPolicy insurance() {
  System.out.println("Domestic Insurance");
  return DomesticInsurance;

public class InternationalInsurance implements Insurance {

 public RecommendedPolicy insurance() {
  System.out.println("International Insurance");
  return InternationalInsurance;


4 Summary

In this article, we explore the Spring Boot annotations. We learned about the different annotations and how to use these annotations to tune Spring Boot auto-configuration process.

Comments are closed.