[java] 'Field required a bean of type that could not be found.' error spring restful API using mongodb

So I've been learning Spring in the couples of week, been following this tutorial

Building a RESTful Web Service

All was well until I tried to integrate it to mongodb. So I follow this tutorial.

Accessing Data with MongoDB

But my practice is partially still using the first one. So my project directory structure is like this.

src/
+-- main/
¦   +-- java/
|       +-- model/
|       |   +-- User.java
|       +-- rest/
|       |   +-- Application.java
|       |   +-- IndexController.java
|       |   +-- UsersController.java
|       +-- service/
|           +-- UserService.java
+-- resources/
    +-- application.properties

This is my model/User.java file

package main.java.model;

import org.springframework.data.annotation.Id;
import org.springframework.data.mongodb.core.mapping.Document;

@Document(collection="user")
public class User {

    private int age;
    private String country; 
    @Id
    private String id;
    private String name;


    public User() {
        super();
    }

    public String getId() {
        return id;
    }

    public void setId(String id) {
        this.id = id;
    }

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public int getAge() {
        return age;
    }

    public void setAge(int age) {
        this.age = age;
    }

    public String getCountry() {
        return country;
    }

    public void setCountry(String country) {
        this.country = country;
    }
}

This is my rest/UsersController.java file

package main.java.rest;

import java.util.List;
import main.java.service.UserService;
import main.java.model.User;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RequestParam;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping(value = "/users")
public class UsersController {

    @Autowired
    UserService userService;

    @RequestMapping(method = RequestMethod.GET)
    public List<User> getAllUsers() {
        return userService.findAll();
    }
}

This is my service/UserService.java file

package main.java.service;

import java.util.List;
import main.java.model.User;
import org.springframework.data.mongodb.repository.MongoRepository;

public interface UserService extends MongoRepository<User, String> {
    public List<User> findAll();
}

I could compile them (I'm using gradle for compilation because I'm following the tutorial), but when I run the jar file it was throwing this error.

---

APPLICATION FAILED TO START

---

Description:

Field userService in main.java.rest.UsersController required a bean of type 'main.java.service.UserService' that could not be found.

Action:

Consider defining a bean of type 'main.java.service.UserService' in your configuration.

Not sure what is wrong I start googling around and found that I need to include Beans.xml file and register the userService in it. I did that but it's not working. I'm really new to this so I really have no clue on what's going on.

My Mapper implementation classes in my target folder had been deleted, so my Mapper interfaces had no implementation classes anymore. Thus I got the same error Field *** required a bean of type ***Mapper that could not be found.

I simply had to regenerate my mappers implementations with maven, and refresh the project...

Two types of mongo dependencies -

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-data-mongodb-reactive</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-data-mongodb</artifactId>
</dependency> 

Two types of repositories -

MongoRepository
ReactiveMongoRepository

Make sure you are using the right combination.

This thread is old now but I am posting my answer, which may be useful for others.

I had the same issue. It turned out that there is another class with the same name in other module. I renamed that class and it solved the issue.

I followed all steps and instructions followed by OP here, took care of blank space around username and password(even though spring takes care of whitespaces in properties file), still was either facing

could not find bean for ___Repository

(you interface which extends JPARepository)

OR after adding @EnableJPARepository

could not find bean for EntityManagerFactory

i solved it by changing spring boot starter parent version from 2.3.2 to 2.2.1 in pom.xml

<parent>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-parent</artifactId>
    <version>2.2.1.RELEASE</version>
    <relativePath /> <!-- lookup parent from repository -->
</parent>

and adding following dependency

<dependency>
    <groupId>mysql</groupId>
    <artifactId>mysql-connector-java</artifactId>
    <scope>runtime</scope>
</dependency>

I did not need to add any of following, spring boot does it itself

1. @EnableJPAReposity - since i already had all class with same root package
2. spring.data.jpa.repositories.enabled in application.properties
3. spring.datasource.driverClassName=com.mysql.jdbc.Driver in application properties

I also had the same error:

***************************
APPLICATION FAILED TO START
***************************

Description:

Field repository in com.kalsym.next.gen.campaign.controller.CampaignController required a bean of type 'com.kalsym.next.gen.campaign.data.CustomerRepository' that could not be found.


Action:

Consider defining a bean of type 'com.kalsym.next.gen.campaign.data.CustomerRepository' in your configuration.de here

And my packages were constructed in the same way as mentioned in the accepted answer. I fixed my issue by adding EnableMongoRepositories annotation in the main class like this:

@SpringBootApplication
@EnableMongoRepositories(basePackageClasses = CustomerRepository.class)
public class CampaignAPI {

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

If you need to add multiple don't forget the curly braces:

@EnableMongoRepositories(basePackageClasses
    = {
        MSASMSRepository.class, APartyMappingRepository.class
    })

Using this solved my issue.

@SpringBootApplication(scanBasePackages={"com.example.something", "com.example.application"})

I know it is old, but wanna add my 5 cents.

I used .service and .service.impl in a folder structure to separate the service with it's implementation. Forget to implement the ServiceImplementation piece.

I have same Issue, fixed by Adding @EnableMongoRepositories("in.topthree.util")

package in.topthree.core;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.data.mongodb.repository.config.EnableMongoRepositories;

import in.topthree.util.Student;

@SpringBootApplication
@EnableMongoRepositories("in.topthree.util")
public class Run implements CommandLineRunner {

    public static void main(String[] args) {
        SpringApplication.run(Run.class, args);
        System.out.println("Run");
    }

    @Autowired
    private Process pr;

    @Override
    public void run(String... args) throws Exception {
        pr.saveDB(new Student("Testing", "FB"));
        System.exit(0);
    }

}

And my Repository is:

package in.topthree.util;

import org.springframework.data.mongodb.repository.MongoRepository;

public interface StudentMongo extends MongoRepository<Student, Integer> {

    public Student findByUrl(String url);
}

Now Its Working

You have to add the @Service annotation to the implementation of your service.

In my case i have just put the Class MyprojectApplication in a package(com.example.start) with the same level of model, controller,service packages.

For me this message:

org.apache.wicket.WicketRuntimeException: Can't instantiate page using constructor 'public org.package.MyClass(org.apache.wicket.request.mapper.parameter.PageParameters)' and argument ''. Might be it doesn't exist, may be it is not visible (public).

meant "in my wicket unit test at the top you have to manually add that bean in like"

appContext.putBean(myClass);

I encountered the same issue and all I had to do was to place the Application in a package one level higher than the service, dao and domain packages.

For anybody who was brought here by googling the generic bean error message, but who is actually trying to add a feign client to their Spring Boot application via the @FeignClient annotation on your client interface, none of the above solutions will work for you.

To fix the problem, you need to add the @EnableFeignClients annotation to your Application class, like so:

@SpringBootApplication
// ... (other pre-existing annotations) ...
@EnableFeignClients // <------- THE IMPORTANT ONE
public class Application {

In this way, the fix is similar to the @EnableMongoRepositories fix mentioned above. It's a shame that this generic error message requires such a tailored fix for every type of circumstance...

Add @Repository in you dao class

example:

@Repository
public class DaoClassName implements IIntefaceDao {
}

I had the same problem I removed the @Autowired Annotation from the controller. If your repository is a class then the Autowired Annotation is needed to use the repository but when it is an interface you do not need to add the @Autowired Annotation from my experience.

Spent a lot of time because of the auto-import. Intellij Idea somewhy imported @Service from import org.jvnet.hk2.annotations.Service; instead of import org.springframework.stereotype.Service;!

Add the @Component in your controller class. May this work

Add the @Service in the service/UserService.java.

Using all @ Annotations fixed my problem. (Yes, I'm new into Spring) If you are using a service class add @Service, and same for @Controller and @Repository.

Then this annotations on the App.java fixed the issue (I'm using JPA + Hibernate)

@SpringBootApplication
@EnableAutoConfiguration(exclude = { ErrorMvcAutoConfiguration.class })
@ComponentScan(basePackages = {"es.unileon.inso2"})
@EntityScan("es.unileon.inso2.model")
@EnableJpaRepositories("es.unileon.inso2.repository")

Package tree:

src/
+-- main/
¦   +-- java/
|       +-- es.unileon.inso2/
|       |   +-- App.java
|       +-- es.unileon.inso2.model/
|       |   +-- User.java
|       +-- es.unileon.inso2.controller/
|       |   +-- IndexController.java
|       |   +-- UserController.java
|       +-- es.unileon.inso2.service/
|       |    +-- UserService.java
|       +-- es.unileon.inso2.repository/
|            +-- UserRepository.java
+-- resources/
    +-- application.properties

I had the same issue. My mistake was that I used @Service annotation on the Service Interface. The @Service annotation should be applied to the ServiceImpl class.

Normally we can solve this problem in two aspects:

1. proper annotation should be used for Spring Boot scanning the bean, like @Component;
2. the scanning path will include the classes just as all others mentioned above.

By the way, there is a very good explanation for the difference among @Component, @Repository, @Service, and @Controller.

In order to spring to create bean and inject it class should be marked with @Componet,@service,@Repository etc in your context it should be

package main.java.service;

import java.util.List;
import main.java.model.User;
import org.springframework.data.mongodb.repository.MongoRepository;
@Repository
public interface UserService extends MongoRepository<User, String> {
    public List<User> findAll();
}

you have to import spring-boot-starter-data-jpa as dependeny if you use spring boot

This may happen when two beans have same names.

Module1Beans.java:

@Configuration
public class Module1Beans {
    @Bean
    public GoogleAPI retrofitService(){
        Retrofit retrofit = new Retrofit.Builder()
                .baseUrl("https://www.google.com/")
                .addConverterFactory(JacksonConverterFactory.create())
                .build();
        return retrofit.create(GoogleAPI.class);
    }
}

Module2Beans.java:

@Configuration
public class Module2Beans {
    @Bean
    public GithubAPI retrofitService(){
        Retrofit retrofit = new Retrofit.Builder()
                .baseUrl("https://www.github.com/")
                .addConverterFactory(JacksonConverterFactory.create())
                .build();
        return retrofit.create(GithubAPI.class);
    }
}

A bean named retrofitService is first created, and it's type is GoogleAPI, then covered by a GithubAPI becauce they're both created by a retrofitService() method. Now when you @Autowired a GoogleAPI you'll get a message like Field googleAPI in com.example.GoogleService required a bean of type 'com.example.rest.GoogleAPI' that could not be found.

Add @Repository in your dao class

    @Repository
    public interface UserDao extends CrudRepository<User, Long> {
         User findByUsername(String username);
         User findByEmail(String email);    
      }

I have come to this post looking for help while using Spring Webflux with Mongo Repository.

My error was similar to owner

Field usersRepository in foobar.UsersService required
a bean of type 'foobar.UsersRepository' that could not be found.

As I was working before with Spring MVC I was surprised by this error.

Because finding help was not so obvious I'm putting answer to this question as it is somehow related and this question is high in search results.

First thing is you must remember about what was mentioned in answer marked as accepted - package hierarchy.

Second important thing is that if you use Webflux you need to use some different package while when using Spring MVC e.g. for MongoDB you need to add

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-data-mongodb-reactive</artifactId>
</dependency>

with -reactive at the end.