javaConfig | Configuration for Java | Configuration Management library

I think that you need to do something like that.

An autowired constructor is invoked if spring invokes the constructor by reflection, typically because you declare the bean using component scanning or XML config. If you manually invoke a constructor in a @Bean method, that constructor executes, and @Autowired has no effect.

An autowired method is invoked after the bean has been created, irrespective of how the bean was created.

The reason is that, in Java, each constructor call creates a new object, making it impossible to call two constructors for the same object. That's why Spring can't call a second constructor if you have already called a different one. In contrast, it is possible to call many methods on the same object, so Spring does support method autowiring just fine.

To conclude, you can use autowiring with JavaConfig, but you should autowire fields or methods rather than constructors. Or you can do without autowiring, and pass everything explicitly in your @Bean method. Or any mixture of the two.

Ok, using the following connection:

Spring identifies the job on the event when we try starting the job. Below is a small snippet for reference,

This is a bean definition which returns of type Job and contains all the orchestration of steps in it,

Spring by default uses JDK dynamic proxies for target classes.

Internally in Java proxies are created using interfaces:

Issue is that spring by default uses XmlWebApplicationContext, so i had to explicitly tell Spring to create application context for web applications by using java clases as input for bean definitions instead of xml files.

Below is the change done to context.xml. This Worked for me.

`

The problem here is that you aren't using autowiring when creating your Hello bean! Instead, you're writing your own factory method hello and calling the constructor directly yourself. @Qualifier is a note that the container reads when it's instantiating the class, not some kind of validation that's baked into the constructor itself (like some tools can do with @Nonnull).

If you need to continue using @Bean, then you'll need to apply the @Qualifier to the method parameter. Even simpler, just apply @Import(Hello.class) to your JavaConfig and let Spring sort this out for you.