How do I configure Spring using Java configuration?

Spring Java configuration lets you configure your application using Java classes instead of XML.

The main annotations are:

  • @Configuration — marks a class as a Spring configuration class
  • @Bean — declares a Spring bean manually
  • @ComponentScan — tells Spring where to find annotated components
  • @PropertySource — loads external properties
  • @Enable... annotations — enable specific Spring features, such as MVC, transactions, JPA, etc.

1. Create a configuration class

import org.springframework.context.annotation.Configuration;

@Configuration
public class AppConfig {
}

@Configuration tells Spring that this class contains bean definitions and application setup.


2. Define beans manually with @Bean

Use @Bean when you want Spring to manage an object that you create yourself.

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;

@Configuration
public class AppConfig {

    @Bean
    public MyService myService() {
        return new MyService();
    }
}

Spring will create and manage the MyService instance.

By default, the bean name is the method name: myService.


3. Use component scanning

Instead of defining every bean manually, you can let Spring discover classes annotated with:

  • @Component
  • @Service
  • @Repository
  • @Controller
  • @RestController

Example:

import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;

@Configuration
@ComponentScan("com.example.app")
public class AppConfig {
}

Then Spring can find beans like this:

import org.springframework.stereotype.Service;

@Service
public class MyService {

    public void doWork() {
        System.out.println("Working...");
    }
}

4. Inject dependencies through constructors

Java configuration works together with dependency injection.

import org.springframework.stereotype.Repository;

@Repository
public class UserRepository {

    public String findNameById(Long id) {
        return "Alice";
    }
}
import org.springframework.stereotype.Service;

@Service
public class UserService {

    private final UserRepository userRepository;

    public UserService(UserRepository userRepository) {
        this.userRepository = userRepository;
    }

    public String getUserName(Long id) {
        return userRepository.findNameById(id);
    }
}

If both classes are discovered by component scanning, Spring automatically injects UserRepository into UserService.


5. Bootstrapping Spring manually

For a non-Spring Boot application, you can start the Spring container like this:

import org.springframework.context.ApplicationContext;
import org.springframework.context.annotation.AnnotationConfigApplicationContext;

public class Main {

    public static void main(String[] args) {
        ApplicationContext context =
                new AnnotationConfigApplicationContext(AppConfig.class);

        MyService myService = context.getBean(MyService.class);
        myService.doWork();
    }
}

6. Configure Spring MVC with Java configuration

For Spring MVC, use @EnableWebMvc and implement WebMvcConfigurer.

import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
import org.springframework.web.servlet.config.annotation.EnableWebMvc;
import org.springframework.web.servlet.config.annotation.WebMvcConfigurer;

@Configuration
@EnableWebMvc
@ComponentScan("com.example.app")
public class WebConfig implements WebMvcConfigurer {
}

Example controller:

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class HelloController {

    @GetMapping("/hello")
    public String hello() {
        return "Hello from Spring MVC";
    }
}

7. Load properties

You can load a properties file with @PropertySource.

import org.springframework.context.annotation.Configuration;
import org.springframework.context.annotation.PropertySource;

@Configuration
@PropertySource("classpath:application.properties")
public class AppConfig {
}

Then inject values with @Value:

import org.springframework.beans.factory.annotation.Value;
import org.springframework.stereotype.Component;

@Component
public class AppInfo {

    private final String appName;

    public AppInfo(@Value("${app.name}") String appName) {
        this.appName = appName;
    }
}

Example application.properties:

app.name=My Spring App

8. Enable transactions

If you use database transactions, enable them with @EnableTransactionManagement.

import org.springframework.context.annotation.Configuration;
import org.springframework.transaction.annotation.EnableTransactionManagement;

@Configuration
@EnableTransactionManagement
public class PersistenceConfig {
}

Then use @Transactional on services:

import org.springframework.stereotype.Service;
import org.springframework.transaction.annotation.Transactional;

@Service
public class OrderService {

    @Transactional
    public void placeOrder() {
        // database operations
    }
}

Typical setup

A common Java configuration setup looks like this:

import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
import org.springframework.context.annotation.PropertySource;
import org.springframework.transaction.annotation.EnableTransactionManagement;

@Configuration
@ComponentScan("com.example.app")
@PropertySource("classpath:application.properties")
@EnableTransactionManagement
public class AppConfig {
}

For Spring MVC:

import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
import org.springframework.web.servlet.config.annotation.EnableWebMvc;
import org.springframework.web.servlet.config.annotation.WebMvcConfigurer;

@Configuration
@EnableWebMvc
@ComponentScan("com.example.app")
public class WebConfig implements WebMvcConfigurer {
}

Summary

To configure Spring using Java configuration:

  1. Create a class annotated with @Configuration.
  2. Add @ComponentScan to discover annotated classes.
  3. Use @Bean methods for manually created beans.
  4. Use constructor injection for dependencies.
  5. Add feature-specific annotations such as @EnableWebMvc, @EnableTransactionManagement, or JPA-related configuration as needed.

In most modern Spring applications, Java configuration plus component scanning replaces XML configuration almost entirely.

How do I create and manage beans in Spring?

In Spring, a bean is an object managed by the Spring container.

Spring is responsible for:

  • creating the object
  • injecting its dependencies
  • managing its lifecycle
  • applying configuration
  • destroying it when the application shuts down

The container that manages beans is usually the ApplicationContext.


1. What Is a Spring Bean?

A Spring bean is just a normal Java object whose lifecycle is controlled by Spring.

For example:

@Service
public class UserService {

    public String getMessage() {
        return "Hello from UserService";
    }
}

UserService is an ordinary Java class, but because it is annotated with @Service, Spring detects it and manages it as a bean.


2. Common Ways to Create Beans

There are two main ways to create beans in Spring:

  1. Component scanning
  2. Manual bean registration using @Bean

Option 1: Create Beans with Component Scanning

This is the most common approach.

Spring scans your project for classes annotated with stereotypes such as:

@Component
@Service
@Repository
@Controller
@RestController

Example:

@Service
public class EmailService {

    public void sendEmail(String to, String message) {
        System.out.println("Sending email to " + to + ": " + message);
    }
}

Spring automatically creates an EmailService bean.


Common Bean Annotations

@Component

Generic Spring-managed component.

@Component
public class FileStorage {
}

Use this when the class does not fit a more specific role.


@Service

Used for service/business logic classes.

@Service
public class PaymentService {
}

@Repository

Used for data access classes.

@Repository
public class UserRepository {
}

In Spring Data JPA, repositories are often interfaces:

@Repository
public interface UserRepository extends JpaRepository<User, Long> {
}

Spring Data JPA creates the implementation automatically.


@Controller

Used for Spring MVC controllers that return views.

@Controller
public class PageController {
}

@RestController

Used for REST APIs.

@RestController
@RequestMapping("/api/users")
public class UserController {
}

@RestController is effectively @Controller plus @ResponseBody.


Option 2: Create Beans Manually with @Bean

Use @Bean when you want to create an object yourself and give it to Spring.

This is common for:

  • third-party classes
  • library objects
  • objects requiring special construction logic
  • configuration-based objects

Example:

@Configuration
public class AppConfig {

    @Bean
    public Clock clock() {
        return Clock.systemUTC();
    }
}

Now Spring manages a Clock bean.

You can inject it elsewhere:

@Service
public class TimeService {

    private final Clock clock;

    public TimeService(Clock clock) {
        this.clock = clock;
    }

    public Instant now() {
        return Instant.now(clock);
    }
}

@Component vs @Bean

Use @Component, @Service, or @Repository when the class is yours and should always be managed by Spring.

Use @Bean when you need explicit construction logic.

Example:

@Configuration
public class HttpClientConfig {

    @Bean
    public HttpClient httpClient() {
        return HttpClient.newBuilder()
                .connectTimeout(Duration.ofSeconds(10))
                .build();
    }
}

Here, HttpClient comes from the JDK, so you cannot annotate it with @Component.


3. Injecting Beans

Once Spring manages a bean, you usually use it through dependency injection.

The recommended style is constructor injection.

@Service
public class OrderService {

    private final PaymentService paymentService;
    private final EmailService emailService;

    public OrderService(PaymentService paymentService, EmailService emailService) {
        this.paymentService = paymentService;
        this.emailService = emailService;
    }

    public void placeOrder() {
        paymentService.charge();
        emailService.sendConfirmation();
    }
}

Spring sees that OrderService needs PaymentService and EmailService, then injects them automatically.


Constructor Injection with Lombok

If your project uses Lombok, you can write:

@Service
@RequiredArgsConstructor
public class OrderService {

    private final PaymentService paymentService;
    private final EmailService emailService;

    public void placeOrder() {
        paymentService.charge();
        emailService.sendConfirmation();
    }
}

@RequiredArgsConstructor generates the constructor for all final fields.

This is common in modern Spring applications.


4. Avoid Field Injection

You may see this style:

@Service
public class OrderService {

    @Autowired
    private PaymentService paymentService;
}

This works, but it is usually discouraged because:

  • it makes testing harder
  • dependencies are hidden
  • fields cannot be final
  • objects can be created in an invalid state

Prefer constructor injection instead.


5. Bean Names

Every bean has a name.

By default, Spring uses the class name with a lowercase-first letter.

@Service
public class PaymentService {
}

Default bean name:

paymentService

You can also give a custom name:

@Service("stripePaymentService")
public class StripePaymentService {
}

Or with @Bean:

@Bean("utcClock")
public Clock clock() {
    return Clock.systemUTC();
}

6. Handling Multiple Beans of the Same Type

If Spring finds multiple beans of the same type, the injection becomes ambiguous.

Example:

public interface PaymentProcessor {
    void process();
}
@Service
public class StripePaymentProcessor implements PaymentProcessor {

    @Override
    public void process() {
        System.out.println("Processing with Stripe");
    }
}
@Service
public class PaypalPaymentProcessor implements PaymentProcessor {

    @Override
    public void process() {
        System.out.println("Processing with PayPal");
    }
}

This is ambiguous:

@Service
public class CheckoutService {

    public CheckoutService(PaymentProcessor paymentProcessor) {
    }
}

Spring does not know which PaymentProcessor to inject.


Use @Primary

Mark one implementation as the default:

@Service
@Primary
public class StripePaymentProcessor implements PaymentProcessor {

    @Override
    public void process() {
        System.out.println("Processing with Stripe");
    }
}

Now Spring injects StripePaymentProcessor unless told otherwise.


Use @Qualifier

Choose a specific bean:

@Service
public class CheckoutService {

    private final PaymentProcessor paymentProcessor;

    public CheckoutService(
            @Qualifier("paypalPaymentProcessor") PaymentProcessor paymentProcessor
    ) {
        this.paymentProcessor = paymentProcessor;
    }
}

The qualifier usually matches the bean name.


7. Bean Scopes

By default, Spring beans are singleton scoped.

That means Spring creates one shared instance per application context.

@Service
public class UserService {
}

This is equivalent to:

@Scope("singleton")
@Service
public class UserService {
}

Common Bean Scopes

singleton

One instance per Spring container.

@Component
@Scope("singleton")
public class AppCache {
}

This is the default.


prototype

A new instance each time the bean is requested.

@Component
@Scope("prototype")
public class ReportBuilder {
}

request

One instance per HTTP request.

@Component
@RequestScope
public class RequestContext {
}

Useful in Spring MVC applications.


session

One instance per HTTP session.

@Component
@SessionScope
public class ShoppingCart {
}

8. Bean Lifecycle

Spring beans go through a lifecycle:

1. Bean definition discovered
2. Object created
3. Dependencies injected
4. Initialization callbacks run
5. Bean is ready to use
6. Destruction callbacks run when context closes

Initialization with @PostConstruct

With Jakarta imports, use:

import jakarta.annotation.PostConstruct;

@Service
public class CacheService {

    @PostConstruct
    public void init() {
        System.out.println("CacheService initialized");
    }
}

Cleanup with @PreDestroy

import jakarta.annotation.PreDestroy;

@Service
public class CacheService {

    @PreDestroy
    public void shutdown() {
        System.out.println("CacheService shutting down");
    }
}

9. Conditional Beans

Sometimes you only want a bean to exist under certain conditions.

In Spring Boot, common annotations include:

@ConditionalOnProperty
@ConditionalOnMissingBean
@ConditionalOnClass
@Profile

Example with profiles:

@Service
@Profile("dev")
public class DevEmailService implements EmailService {
}
@Service
@Profile("prod")
public class SmtpEmailService implements EmailService {
}

Run with:

spring.profiles.active=prod

Then only the prod bean is active.


10. Configuration Properties as Beans

For application configuration, prefer configuration properties instead of manually reading values.

@ConfigurationProperties(prefix = "mail")
public class MailProperties {

    private String host;
    private int port;

    public String getHost() {
        return host;
    }

    public void setHost(String host) {
        this.host = host;
    }

    public int getPort() {
        return port;
    }

    public void setPort(int port) {
        this.port = port;
    }
}

Enable it:

@Configuration
@EnableConfigurationProperties(MailProperties.class)
public class MailConfig {
}

Example config:

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

Then inject it:

@Service
public class MailService {

    private final MailProperties mailProperties;

    public MailService(MailProperties mailProperties) {
        this.mailProperties = mailProperties;
    }
}

11. Getting Beans Programmatically

Most of the time, you should not call ApplicationContext#getBean() manually.

Prefer this:

@Service
public class ReportService {

    private final CsvExporter csvExporter;

    public ReportService(CsvExporter csvExporter) {
        this.csvExporter = csvExporter;
    }
}

Instead of this:

@Service
public class ReportService {

    private final ApplicationContext applicationContext;

    public ReportService(ApplicationContext applicationContext) {
        this.applicationContext = applicationContext;
    }

    public void export() {
        CsvExporter exporter = applicationContext.getBean(CsvExporter.class);
    }
}

Programmatic lookup is sometimes useful for dynamic behavior, but it should not be your default approach.


12. Dynamic or Lazy Bean Access

If you need lazy or optional access, prefer ObjectProvider.

@Service
public class NotificationService {

    private final ObjectProvider<SmsSender> smsSenderProvider;

    public NotificationService(ObjectProvider<SmsSender> smsSenderProvider) {
        this.smsSenderProvider = smsSenderProvider;
    }

    public void notifyUser(String phoneNumber, String message) {
        SmsSender smsSender = smsSenderProvider.getIfAvailable();

        if (smsSender != null) {
            smsSender.send(phoneNumber, message);
        }
    }
}

This avoids directly depending on ApplicationContext.


13. Lazy Beans

By default, singleton beans are usually created during application startup.

You can make a bean lazy:

@Service
@Lazy
public class ExpensiveService {
}

Or inject it lazily:

@Service
public class DashboardService {

    private final ExpensiveService expensiveService;

    public DashboardService(@Lazy ExpensiveService expensiveService) {
        this.expensiveService = expensiveService;
    }
}

14. Managing Beans in Tests

In Spring tests, beans can be injected into test classes:

@SpringBootTest
class OrderServiceTest {

    @Autowired
    private OrderService orderService;

    @Test
    void placesOrder() {
        orderService.placeOrder();
    }
}

You can replace beans with mocks using Spring Boot testing support:

@SpringBootTest
class OrderServiceTest {

    @MockBean
    private PaymentService paymentService;

    @Autowired
    private OrderService orderService;

    @Test
    void placesOrder() {
        orderService.placeOrder();
    }
}

For plain unit tests, you often do not need Spring:

class OrderServiceTest {

    @Test
    void placesOrder() {
        PaymentService paymentService = mock(PaymentService.class);
        EmailService emailService = mock(EmailService.class);

        OrderService orderService = new OrderService(paymentService, emailService);

        orderService.placeOrder();
    }
}

15. Practical Rules

Use these rules most of the time:

  1. Use @Service for business logic.
  2. Use @Repository for persistence/data access.
  3. Use @Controller or @RestController for web endpoints.
  4. Use @Component for general Spring-managed classes.
  5. Use @Bean for third-party objects or special construction logic.
  6. Prefer constructor injection.
  7. Avoid field injection.
  8. Avoid calling ApplicationContext#getBean() unless you truly need dynamic lookup.
  9. Use @Qualifier or @Primary when multiple beans share the same type.
  10. Keep singleton beans stateless when possible.

Minimal Example

@Service
public class GreetingService {

    public String greet(String name) {
        return "Hello, " + name;
    }
}
@RestController
@RequestMapping("/greetings")
public class GreetingController {

    private final GreetingService greetingService;

    public GreetingController(GreetingService greetingService) {
        this.greetingService = greetingService;
    }

    @GetMapping("/{name}")
    public String greet(@PathVariable String name) {
        return greetingService.greet(name);
    }
}

Spring will:

1. Find GreetingService
2. Create a GreetingService bean
3. Find GreetingController
4. Create a GreetingController bean
5. Inject GreetingService into GreetingController
6. Map GET /greetings/{name}
7. Call the controller method when a request arrives

Bottom Line

To create and manage beans in Spring:

  • annotate your classes with @Component, @Service, @Repository, or @Controller
  • define special beans with @Bean inside @Configuration
  • inject dependencies through constructors
  • let Spring manage lifecycle, scopes, configuration, and wiring

In most cases, you should declare what your application needs and let Spring create and connect the objects for you.

How do I use dependency injection in Spring?

In Spring, Dependency Injection (DI) means you let the Spring container create and provide the objects your class depends on, instead of manually creating them with new.

The recommended approach in modern Spring is constructor injection.

1. Define a dependency as a Spring bean

import org.springframework.stereotype.Component;

@Component
public class EmailSender {

    public void send(String message) {
        System.out.println("Sending email: " + message);
    }
}

@Component tells Spring: “Create and manage an instance of this class.”

2. Inject it into another bean

import org.springframework.stereotype.Service;

@Service
public class NotificationService {

    private final EmailSender emailSender;

    public NotificationService(EmailSender emailSender) {
        this.emailSender = emailSender;
    }

    public void notifyUser(String message) {
        emailSender.send(message);
    }
}

Because NotificationService is also a Spring bean, Spring sees its constructor and automatically provides an EmailSender.

In modern Spring, if there is only one constructor, you usually do not need @Autowired on the constructor.

3. Use the service from a controller or another bean

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class NotificationController {

    private final NotificationService notificationService;

    public NotificationController(NotificationService notificationService) {
        this.notificationService = notificationService;
    }

    @GetMapping("/notify")
    public String notifyUser() {
        notificationService.notifyUser("Hello from Spring!");
        return "Notification sent";
    }
}

Common DI styles in Spring

Constructor injection — recommended

@Service
public class MyService {

    private final MyDependency myDependency;

    public MyService(MyDependency myDependency) {
        this.myDependency = myDependency;
    }
}

Use this most of the time because it:

  • makes dependencies explicit
  • supports immutability with final
  • is easier to test
  • avoids partially initialized objects

Setter injection

@Service
public class MyService {

    private MyDependency myDependency;

    @Autowired
    public void setMyDependency(MyDependency myDependency) {
        this.myDependency = myDependency;
    }
}

Use setter injection mainly for optional dependencies or dependencies that may change after construction.

Field injection — usually avoid

@Service
public class MyService {

    @Autowired
    private MyDependency myDependency;
}

This works, but it is generally discouraged because it makes testing harder and hides the class’s required dependencies.

Injecting interfaces

A common pattern is to inject an interface rather than a concrete class:

public interface MessageSender {
    void send(String message);
}
import org.springframework.stereotype.Component;

@Component
public class EmailSender implements MessageSender {

    @Override
    public void send(String message) {
        System.out.println("Email: " + message);
    }
}
import org.springframework.stereotype.Service;

@Service
public class NotificationService {

    private final MessageSender messageSender;

    public NotificationService(MessageSender messageSender) {
        this.messageSender = messageSender;
    }

    public void notifyUser(String message) {
        messageSender.send(message);
    }
}

If there is only one implementation of MessageSender, Spring injects it automatically.

When there are multiple implementations

If multiple beans match the same type, use @Qualifier:

import org.springframework.beans.factory.annotation.Qualifier;
import org.springframework.stereotype.Service;

@Service
public class NotificationService {

    private final MessageSender messageSender;

    public NotificationService(@Qualifier("emailSender") MessageSender messageSender) {
        this.messageSender = messageSender;
    }
}

The qualifier value usually matches the bean name, which by default is the class name with a lowercase-first letter.

Creating beans with @Bean

You can also define beans in a configuration class:

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;

@Configuration
public class AppConfig {

    @Bean
    public EmailSender emailSender() {
        return new EmailSender();
    }
}

This is useful when:

  • the class comes from a third-party library
  • construction requires custom setup
  • you do not want to annotate the class with @Component

Summary

Use this pattern most of the time:

@Service
public class MyService {

    private final MyDependency myDependency;

    public MyService(MyDependency myDependency) {
        this.myDependency = myDependency;
    }

    public void doWork() {
        myDependency.doSomething();
    }
}

And make sure the dependency is a Spring bean:

@Component
public class MyDependency {

    public void doSomething() {
        System.out.println("Dependency logic executed.");
    }
}

In short: annotate your classes with Spring stereotypes like @Component, @Service, or @Repository, then inject dependencies through constructors.

How do I understand what the Spring Framework actually does?

The easiest way to understand what the Spring Framework actually does is to stop thinking of it as “magic” and start thinking of it as infrastructure code that your application delegates to.

At a high level:

Spring creates objects, wires them together, manages their lifecycle, and adds common behavior around them so you do not have to write that plumbing yourself.


1. The Core Problem Spring Solves

Without Spring, your application code often has to manually do things like:

UserRepository repository = new JdbcUserRepository(dataSource);
EmailService emailService = new SmtpEmailService(config);
UserService userService = new UserService(repository, emailService);

As the application grows, this becomes harder to manage:

  • Who creates each object?
  • In what order?
  • Which implementation should be used?
  • How are shared dependencies reused?
  • How do you add transactions, security, logging, validation, configuration, etc.?

Spring’s answer is:

Declare your application components, and I will create, connect, configure, and enhance them.


2. Spring Is Mainly an Application Container

The heart of Spring is the IoC container.

IoC means Inversion of Control.

Instead of your code controlling object creation:

UserService service = new UserService(new UserRepository());

Spring controls it:

@Service
public class UserService {

    private final UserRepository userRepository;

    public UserService(UserRepository userRepository) {
        this.userRepository = userRepository;
    }
}

Then Spring sees:

@Repository
public class UserRepository {
}

And automatically creates:

  • a UserRepository
  • a UserService
  • injects the repository into the service

This is called Dependency Injection.

So Spring’s first major job is:

Managing your application objects, called beans.


3. What Is a Bean?

A Spring bean is simply an object managed by Spring.

For example:

@Service
public class PaymentService {
}

That class becomes a Spring-managed object.

Spring can:

  • create it
  • inject its dependencies
  • configure it
  • call lifecycle methods
  • wrap it with proxies
  • destroy it when the application shuts down

The object itself is ordinary Java. What changes is who manages it.


4. Spring Reads Metadata About Your App

Spring needs to know what objects to manage.

You give it metadata using annotations such as:

@Component
@Service
@Repository
@Controller
@Configuration
@Bean
@Autowired

Example:

@Configuration
public class AppConfig {

    @Bean
    public Clock clock() {
        return Clock.systemUTC();
    }
}

This tells Spring:

“When something needs a Clock, use this object.”

Spring scans your code, reads these annotations, builds a registry of beans, and creates an application context.


5. The ApplicationContext Is the Running Spring Container

The ApplicationContext is basically Spring’s runtime environment.

It contains all managed beans.

Conceptually:

ApplicationContext context = ...;

UserService userService = context.getBean(UserService.class);

In most Spring applications, you do not usually call getBean() yourself. Spring injects dependencies automatically.

The container knows:

  • which beans exist
  • how to create them
  • what dependencies they need
  • what order to initialize them in
  • what configuration values they require

6. Spring Adds Behavior Using Proxies

A lot of Spring’s “magic” comes from proxies.

For example, when you write:

@Transactional
public void transferMoney(Account from, Account to, BigDecimal amount) {
    withdraw(from, amount);
    deposit(to, amount);
}

Spring does not rewrite your method.

Instead, it may create a wrapper object around your service.

Conceptually:

beginTransaction();

try {
    transferMoney(...);
    commitTransaction();
} catch (Exception ex) {
    rollbackTransaction();
    throw ex;
}

That wrapper is a proxy.

Spring uses proxies for features like:

  • transactions
  • security
  • caching
  • async methods
  • method validation
  • aspect-oriented programming

So another major thing Spring does is:

It intercepts calls to your objects and adds infrastructure behavior around them.


7. Spring MVC Handles Web Requests

If you use Spring MVC, Spring also acts as a web framework.

You write:

@RestController
@RequestMapping("/users")
public class UserController {

    @GetMapping("/{id}")
    public UserDto getUser(@PathVariable Long id) {
        return new UserDto(id, "Alice");
    }
}

Spring MVC handles:

  • receiving the HTTP request
  • matching /users/{id} to the method
  • converting path variables
  • calling your controller
  • converting the return value to JSON
  • writing the HTTP response

You focus on:

public UserDto getUser(Long id)

Spring handles the web plumbing.


8. Spring Data JPA Creates Repository Implementations

With Spring Data JPA, you can write:

public interface UserRepository extends JpaRepository<User, Long> {
    Optional<User> findByEmail(String email);
}

You do not manually implement this interface.

Spring Data creates an implementation at runtime.

It understands method names like:

findByEmail
findByStatus
findByCreatedAtAfter

And turns them into database queries.

So Spring Data JPA does:

  • repository implementation generation
  • query method parsing
  • transaction integration
  • JPA EntityManager management

9. Spring Boot vs Spring Framework

This is an important distinction.

Spring Framework

The Spring Framework provides the core capabilities:

  • dependency injection
  • bean lifecycle
  • transactions
  • Spring MVC
  • validation integration
  • resource loading
  • AOP
  • event system

Spring Boot

Spring Boot sits on top of Spring Framework.

It adds:

  • auto-configuration
  • embedded servers
  • starter dependencies
  • production features
  • simplified project setup

Spring Boot’s job is mostly:

“Based on what dependencies and settings you have, I will configure Spring automatically.”

For example, if Spring Boot sees Spring MVC on the classpath, it configures a web server and MVC infrastructure.

If it sees Spring Data JPA and a database driver, it configures JPA-related beans.


10. A Mental Model

Think of a Spring application like this:

Your code:
  Controllers
  Services
  Repositories
  Entities
  Configuration

Spring:
  Creates objects
  Injects dependencies
  Applies configuration
  Opens transactions
  Handles HTTP requests
  Converts JSON
  Manages validation
  Integrates with databases
  Publishes events
  Handles lifecycle

You write the business logic.

Spring handles the surrounding infrastructure.


11. What Happens at Startup?

Simplified startup flow:

1. Application starts
2. Spring creates an ApplicationContext
3. Spring scans classes and configuration
4. Spring discovers bean definitions
5. Spring creates beans
6. Spring injects dependencies
7. Spring applies post-processors
8. Spring creates proxies where needed
9. Web server starts, if this is a web app
10. App is ready to receive requests

For example:

@SpringBootApplication
public class MyApplication {

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

That one line starts a large amount of framework infrastructure.


12. A Practical Way to Learn Spring

To understand Spring deeply, learn it in this order:

  1. Plain Java object creation
  2. Dependency Injection
  3. Beans and ApplicationContext
  4. Configuration with @Configuration and @Bean
  5. Component scanning with @Component, @Service, @Repository
  6. Bean lifecycle
  7. Spring MVC request handling
  8. Transactions with @Transactional
  9. Spring Data repositories
  10. Spring Boot auto-configuration

Avoid starting with everything at once. Spring feels magical when you learn MVC, JPA, transactions, Boot, security, and annotations simultaneously.


13. Tiny Example

Your code:

@Service
public class GreetingService {

    public String greet(String name) {
        return "Hello, " + name;
    }
}
@RestController
public class GreetingController {

    private final GreetingService greetingService;

    public GreetingController(GreetingService greetingService) {
        this.greetingService = greetingService;
    }

    @GetMapping("/hello")
    public String hello() {
        return greetingService.greet("World");
    }
}

What Spring does:

1. Finds GreetingService
2. Creates a GreetingService object
3. Finds GreetingController
4. Sees that it needs GreetingService
5. Injects GreetingService into GreetingController
6. Maps GET /hello to hello()
7. Calls hello() when an HTTP request arrives
8. Sends "Hello, World" as the response

That is Spring in miniature.


Bottom Line

Spring Framework mainly does four things:

  1. Object management
    It creates and manages your application objects.

  2. Dependency injection
    It wires objects together automatically.

  3. Infrastructure integration
    It provides transactions, web handling, validation, database integration, events, configuration, etc.

  4. Behavior wrapping
    It uses proxies to add behavior such as transactions, security, caching, and async execution.

The shortest explanation is:

Spring is a container and infrastructure framework that lets you write business code while it handles object creation, wiring, lifecycle, and common enterprise concerns.

How do I use dependency injection with aspect-oriented programming (AOP) in Spring?

In Spring, Dependency Injection (DI) and Aspect-Oriented Programming (AOP) can work seamlessly together, allowing you to address cross-cutting concerns (e.g., logging, transaction management, security) while still benefiting from Spring’s dependency management.

Here’s how you can use Dependency Injection with AOP in Spring:

1. Enable Aspect-Oriented Programming in Spring

To enable the AOP functionality in your Spring application, you need to add the @EnableAspectJAutoProxy annotation to your configuration class (usually the class annotated with @Configuration or your main class with @SpringBootApplication).

For example:

@Configuration
@EnableAspectJAutoProxy
public class AppConfig {
    // Configuration beans can go here
}

The @EnableAspectJAutoProxy annotation enables support for processing aspects using Spring AOP.

2. Create an Aspect

An aspect is a modularization of a cross-cutting concern, implemented as a Java class annotated with @Aspect and registered as a Spring component (@Component or declared as a @Bean).

Example:

import org.aspectj.lang.annotation.Aspect;
import org.aspectj.lang.annotation.Before;
import org.springframework.stereotype.Component;

@Aspect
@Component
public class LoggingAspect {

    @Before("execution(* com.example.service.*.*(..))")
    public void logBeforeMethodExecution() {
        System.out.println("Method is about to execute");
    }
}

Here:

  • @Aspect: Annotates the class as an aspect.
  • @Before: Specifies a pointcut expression where the advice (logic) will execute before the matched method runs.
  • In the example above, the pointcut expression matches all methods in the com.example.service package.

3. Use Dependency Injection in the Aspect

You can inject dependencies into your aspect just like any other Spring-managed component. For example, if your aspect requires a specific service or repository, you can inject it using @Autowired or constructor injection.

Example:

import org.aspectj.lang.annotation.Aspect;
import org.aspectj.lang.annotation.Before;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Component;

@Aspect
@Component
public class LoggingAspect {

    private final MyService myService;

    @Autowired
    public LoggingAspect(MyService myService) {
        this.myService = myService;
    }

    @Before("execution(* com.example.service.*.*(..))")
    public void logBeforeMethodExecution() {
        myService.performAction(); // Example of using a DI-provided dependency in the aspect
        System.out.println("Method is about to execute with dependency injected.");
    }
}

In this example:

  • MyService is a Spring-managed bean that is injected into the LoggingAspect class.
  • The aspect can now use the injected service (MyService) to perform its tasks.

4. Define Regular Spring Beans for DI

Make sure the dependencies to be injected into your aspect are defined as Spring beans in your application context. For instance:

@Service
public class MyService {
    public void performAction() {
        System.out.println("MyService action performed.");
    }
}

5. Use Aspects with Application Code

With the aspect configured and dependencies injected, simply use the relevant Spring services or beans as usual. The aspect advice will be triggered based on the defined pointcut.

Example service code:

@Service
public class ExampleService {
    public void sampleMethod() {
        System.out.println("Executing the target method.");
    }
}

When you call sampleMethod on (e.g., via an @Autowired bean in a controller or main class), the LoggingAspect advice will be triggered before the method execution. ExampleService

Key Points

  1. Spring AOP works with Spring proxies, which means the aspect logic is weaved during runtime for Spring-managed components.
  2. Dependency injection works seamlessly in aspects, as long as the aspect itself is a Spring-managed bean.
  3. Configure pointcuts properly to ensure they match the intended methods or classes.
  4. Test your application to ensure aspects and dependency injection are working as expected.

This approach ensures that your AOP and DI are well-integrated in your Spring application.