Application Entry Point and Core Annotations

A standard Spring Boot application typically begins with a primary class containing the main method. This class serves as the bootstrap for the Java application. The most critical component here is the @SpringBootApplication annotation, which acts as a composite marker for the framework.

This annotation combines three distinct functionalities:

• @SpringBootConfiguration: Indicates that the class provides configuration for the application context. It is a specialized form of @Configuration preferred within the Spring Boot ecosystem.
• @EnableAutoConfiguration: Triggers the auto-configuration mechanism. Based on the dependencies present in the classpath (such as spring-boot-starter-web), Spring Boot automatically configures beans like Tomcat or Spring MVC.
• @ComponentScan: Directs Spring to scan for components in the current package and sub-packages. Filters can be applied to exclude specific types from being registered as beans.

Example of a bootstrap class:

package org.example.project;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class Bootstrapper {
    public static void main(String[] args) {
        SpringApplication.run(Bootstrapper.class, args);
    }
}

Managing Auto-Configuration

While auto-configuration accelerates development by inferring settings from jar dependencies, it may introduce unnecessary overhead during startup if certain components are not required. To optimize initialization time, spceific auto-configuration classes can be disabled.

For instance, if the project includes Redis dependencies but automatic configuration is not desired, you can exclude the relevant configuration class directly in the annotation:

@SpringBootApplication(exclude = {
    org.springframework.boot.autoconfigure.data.redis.RedisAutoConfiguration.class
})
public class Bootstrapper { ... }

Customizing the Startup Banner

Upon launching, Spring Boot prints a default banner to the console. This ASCII art can be personalized. Developers can use online text art generators to create custom designs. The generated content should be saved into a file named banner.txt.

Place this file within the src/main/resources directory. When the application restarts, the console will display the new custom banner instead of the default Spring logo.

Global Configuration Properties

Spring Boot utilizes a global configuration file, typically named application.properties or application.yml, located in the resources directory or under config on the classpath. This file allows overriding default settings.

Common modifications include changing the embedded server port or adjusting servlet mapping rules:

# Change the embedded Tomcat port
server.port=9090

# Modify the DispatcherServlet URL pattern
spring.mvc.servlet.path=*.action

The framework supports a vast array of properties covering core settings, logging, security, data access, and more. Below are selected examples of configurable properties often used in production environments:

# ----------------------------------------
# SERVER CONFIGURATION
# ----------------------------------------
server.address=0.0.0.0
server.compression.enabled=true
server.servlet.context-path=/api
server.ssl.enabled=false

# ----------------------------------------
# LOGGING SETTINGS
# ----------------------------------------
logging.file.name=app.log
logging.level.root=INFO
logging.level.org.springframework.web=DEBUG
logging.pattern.console=%d{yyyy-MM-dd} - %msg%n

# ----------------------------------------
# DATABASE CONFIGURATION
# ----------------------------------------
spring.datasource.url=jdbc:mysql://localhost:3306/db
spring.datasource.username=admin
spring.datasource.password=secret
spring.jpa.hibernate.ddl-auto=update

# ----------------------------------------
# SECURITY SETTINGS
# ----------------------------------------
spring.security.user.name=admin
spring.security.user.password=securePassword123

Starter POM Dependencies

Spring Boot simplifies dependency management through "Starter" POMs. Including a specific starter (e.g., for web development or data access) automatically pulls in the necessary libraries and triggers corresponding auto-configuration beans. This reduces the need for manual version management and explicit bean definition.

Advanced Configuration Options

Although Spring Boot favors annotation-based configuration, legacy XML configurations can still be integrated using the @ImportResource annotation.

@ImportResource(locations = {"classpath:legacy-context.xml"})
@SpringBootApplication
public class Bootstrapper { ... }

Additionally, logging behavior can be fine-tuned via the properties file. Log levels for specific packages can be adjusted to control verbosity during runtime:

# Set specific package logging to DEBUG
logging.level.org.springframework=DEBUG
logging.level.com.example.service=INFO