In our application, we have a lot of objects. These objects are components of our application. When we want Spring to create, manage, and inject these objects, they are considered Spring beans.<\/p>\n\n\n\n
The When starting the application context, Spring will look for these This annotation is usually placed in configuration classes. As we know, Spring already has some auto-configuration for resources like Spring Kafka, Spring Cache, etc.<\/p>\n\n\n\n But if you want to create and manage a custom resource, like a custom notification service, using the In some cases, we can use the Let’s take a look.<\/p>\n\n\n\n In this scenario, our application must use a custom SMTP service to send emails. We can create a method to instantiate the service as we need and return the object. Since we want this to become a bean, we annotate the method with @Bean<\/code> annotation is a method-level annotation that we can use to tell Spring that we want it to manage the instance for us.<\/p>\n\n\n\n@Bean<\/code> methods and add them to the IoC container to manage their lifecycle so that other components can inject and use them.<\/p>\n\n\n\n@Bean<\/code> to make this custom bean available in your application is the way to go.<\/p>\n\n\n\n@Bean<\/code> annotation to customize some auto-configured beans. This allows us to replace the default configuration with a modified version that suits our needs.<\/p>\n\n\n\nCreating a Custom Bean<\/h3>\n\n\n\n
@Bean<\/code> to tell Spring to put this object in the Spring IoC as a bean.<\/p>\n\n\n\n