Spring Bean Definition Explained

Direct Answer

A Spring bean definition is metadata that tells the container how to create and manage an object. It can describe the bean class or factory method, scope, constructor arguments, property values, qualifiers, lazy behavior, and lifecycle methods. The BeanFactory stores definitions; the actual bean instance may be created later according to its scope and lazy settings.

Code Example

import org.springframework.context.annotation.AnnotationConfigApplicationContext;
import org.springframework.stereotype.Service;

@Service
class OrderService {
    private final PaymentGateway gateway;
    public OrderService(PaymentGateway gateway) { this.gateway = gateway; }
}

@Service
class PaymentGateway {}

public class BeanDefinitionDemo {
    public static void main(String[] args) {
        var context = new AnnotationConfigApplicationContext("com.example");
        
        // Bean definition exists before bean instance is created
        var definition = context.getBeanDefinition("orderService");
        System.out.println("Bean class: " + definition.getBeanClassName());
        System.out.println("Scope: " + definition.getScope()); // singleton
        System.out.println("Lazy init: " + definition.isLazyInit()); // false
        
        // Now get the actual instance (created from the definition)
        var service = context.getBean(OrderService.class);
    }
}

Common Mistakes & Pitfalls

• Confusing definition with instance: Freshers often think getBeanDefinition and getBean return the same thing. The definition is metadata; the instance is the living object. Modifying a definition after startup doesn't change existing singletons.
• Expecting definitions to exist for manual new calls: If you write new OrderService(gateway) instead of injecting it, Spring has no bean definition for that instance—it won't be managed, proxied, or eligible for @Transactional.
• Not realizing definitions are created at startup: All definitions are registered during application context refresh, before any bean is instantiated. If a class isn't scanned (wrong package) or lacks @Component, no definition exists and you'll get NoSuchBeanDefinitionException at runtime.