NoSuchBeanDefinitionException: No qualifying bean of type available: expected at least 1 bean which qualifies as autowire candidate

Question

I am trying to migrate a Spring 4.x.x to Spring boot and it has a dependency on a class in external spring 2.5 jar. I have made all the autowiring changes and below is my application class

@SpringBootApplication
@EnableAutoConfiguration
@ComponentScan(basePackages = { "com.xyz" })
public class MainApiApplication {

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

The dependent class in the external jar is present under the package com.xyz.abc because of which I have placed my main application class under com.xyz package and also added the component scan under the same package

Here are my component classes with the dependency autowired

@Component
public class ComponentClassA {
    @Autowired
    private ComponentClassB currencyService;
}

@Component
public class ComponentClassB {

    @Autowired
    private DependentClass depClass;
}

DependentClass is the class present in the external dependent jar which I have locally attached and built

When building the application, compilation of all files is fine and build is generated successfully. But when I start the application, I get the below error

 Field DependentClass in com.xyz.ComponentClassB required a bean of type 'com.xyz.common.util.DependentClass' that could not be found.

I don't understand the reason for the class from external jar being not found as I have added component scan for the package

The definition of DependentClass is like below

public class DependentClass extends ResourceClass<Map<String, Double>> {
            // Methods and logic
}

Is it because DependentClass is extending a class ? Can someone help me figure out the reason for the error ?

Does your `DependentClass` exist as a Bean within the Spring context (either xml or `@Bean` annotation)? — Ultcyber, Jul 17 '18 at 15:11
It should be a bean then only Auto wiring will work. Better to create a bean in you @Configuration file and then do Autowiring. — Sachin, Jul 17 '18 at 15:25
Yes, as others mentioned, it should be registered as a Bean then. If you don't / can't modify the classes in the .jar file, I would suggest using xml configuration — Ultcyber, Jul 17 '18 at 16:04
use @Bean public DependentClass depClass(){ return new DependentClass(); } — Vishal Monga, Jul 18 '18 at 06:55

Sanjeev Sachdev · Answer 1 · 2018-07-17T15:33:28.423

5

The DependentClass does not have @Component annotation on it. So, you need to create a bean of DependentClass yourself either via XML or Java config.

And it is not necessary that you place your main class under the same package as DependentClass.

edited Jul 17 '18 at 15:33

answered Jul 17 '18 at 15:24

Sanjeev Sachdev

1,241
1
15
23

Vishal Monga · Answer 2 · 2018-07-18T06:54:10.773

1

Define your class as per below:-

     @Component("depClass") 
     public class DependentClass extends ResourceClass<Map<String, Double>> {
            // Methods and logic
      }

Component register it into your context defination if this package lie into your ScanBasePackages and the depClass inside the component annotation define the name of your bean.

you can also call it by:-

    @Autowired
    @Qualifier("depClass")
    private DependentClass dependentClass;

If that class define in your external class then use @Bean annotaion like:-

 @Bean
   public DependentClass depClass(){
    return new DependentClass();
   }

After that Autowired the class you get the instance finally.

edited Jul 18 '18 at 06:54

answered Jul 18 '18 at 06:46

Vishal Monga

272
2
14

This way by defining the already existing class from the jar, I am duplicating it know! Is this the only way ? – Aarish Ramesh Jul 18 '18 at 07:10
As per my perspective this is the only way that i use,may be there are more things to define the class.If i find another way then i also share with you. – Vishal Monga Jul 18 '18 at 07:15

score 0 · Answer 3 · answered Jul 17 '18 at 15:34

0

DependentClass is not defined in your current Spring Context.DependentClass is not annotated with a bean (@Bean).Hence nosuchbeandefinitionexception occurs.

@Bean
public class DependentClass extends ResourceClass<Map<String, Double>> {
            // Methods and logic
}

answered Jul 17 '18 at 15:34

Bala Vignesh S

1
1

2

`@Bean` annotation is not allowed on classes or interfaces; the code you pasted will not compile – raner Dec 18 '20 at 00:47

NoSuchBeanDefinitionException: No qualifying bean of type available: expected at least 1 bean which qualifies as autowire candidate

3 Answers3