Tips on how to Repair Take into account defining a bean of kind ‘package deal’ in your configuration [Solved]

By following these steps, it’s best to be capable to resolve the “Take into account defining a bean of kind ‘package deal’ in your configuration” error and efficiently begin your Spring Boot software. For higher understanding, I’ll present you find out how to clear up this error with the assistance of an instance. Beneath are the courses in my easy Spring Boot mission.

SpringBootPracticeApplication.java

package deal com.follow.springboot.fundamental;



import com.follow.springboot.entity.Worker;

import com.follow.springboot.repo.EmployeeRepo;

import org.springframework.beans.manufacturing unit.annotation.Autowired;

import org.springframework.boot.CommandLineRunner;

import org.springframework.boot.SpringApplication;

import org.springframework.boot.autoconfigure.SpringBootApplication;



@SpringBootApplication

public class SpringBootPracticeApplication implements CommandLineRunner {

   @Autowired

   EmployeeRepo employeeRepo;

   public static void fundamental(String[] args) {

      SpringApplication.run(SpringBootPracticeApplication.class, args);

   }

   @Override

   public void run(String... args) throws Exception {

      Worker worker = new Worker();

      worker.setName("John");

      worker.setAge(25);

      worker.setSalary(10000);

      worker.setQualification("BE");



      

      employeeRepo.save(worker); 

   }

}

Worker.java

package deal com.follow.springboot.entity;

import jakarta.persistence.*;

import lombok.Information;



@Entity

@Desk(identify = "staff")

public class Worker {

    @Id

    @GeneratedValue(technique = GenerationType.AUTO)

    personal int id;

    personal String identify;

    personal int age;

    personal double wage;

    personal String qualification;



}

EmployeeController.java

package deal com.follow.springboot.controller;



import com.follow.springboot.repo.EmployeeRepo;

import org.springframework.beans.manufacturing unit.annotation.Autowired;

import org.springframework.http.HttpStatus;

import org.springframework.http.ResponseEntity;

import org.springframework.internet.bind.annotation.RequestMapping;

import org.springframework.internet.bind.annotation.RequestMethod;

import org.springframework.internet.bind.annotation.RestController;



@RestController

@RequestMapping("/api/v1")

public class EmployeeController {



    @Autowired

    EmployeeRepo employeeRepo;



    @RequestMapping(worth = "/staff", methodology = RequestMethod.GET)

    public ResponseEntity<?> getEmployees(){

        return new ResponseEntity<>(employeeRepo.findAll(), HttpStatus.OK);

    }

}

EmployeeRepo.java

package deal com.follow.springboot.repo;



import com.follow.springboot.entity.Worker;

import org.springframework.knowledge.jpa.repository.JpaRepository;



public interface EmployeeRepo extends JpaRepository<Worker,Integer> {



}

Right here is our software’s listing construction.

├── fundamental

│   ├── java

│   │   └── com

│   │       └── follow

│   │           └── springboot

│   │               ├── controller

│   │               │   └── EmployeeController.java

│   │               ├── entity

│   │               │   └── Worker.java

│   │               ├── fundamental

│   │               │   └── SpringBootPracticeApplication.java

│   │               ├── repo

│   │               │   └── EmployeeRepo.java

│   │               └── service

│   └── sources

│       ├── software.properties

│       ├── static

│       └── templates

└── take a look at

    └── java

        └── com

            └── follow

                └── springboot

                    └── SpringBootPracticeApplicationTests.java

After we run our fundamental software, the next outcomes will seem within the console window.

.   ____          _            __ _ _

 / / ___’_ __ _ _(_)_ __  __ _

( ( )___ | ‘_ | ‘_| | ‘_ / _` |

 /  ___)| |_)| | | | | || (_| |  ) ) ) )

  ‘  |____| .__|_| |_|_| |___, | / / / /

 =========|_|==============|___/=/_/_/_/

 :: Spring Boot ::                (v3.0.4)

2023-03-09T15:29:17.410+05:00  INFO 45556 — [           main] .s.d.r.c.RepositoryConfigurationDelegate : Completed Spring Information repository scanning in 16 ms. Discovered 0 JPA repository interfaces.

2023-03-09T15:29:17.812+05:00  INFO 45556 — [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)

Loading class `com.mysql.jdbc.Driver’. That is deprecated. The brand new driver class is `com.mysql.cj.jdbc.Driver’. The motive force is robotically registered by way of the SPI and guide loading of the driving force class is usually pointless.

2023-03-09T15:29:18.448+05:00  INFO 45556 — [           main] SQL dialect                              : HHH000400: Utilizing dialect: org.hibernate.dialect.MySQLDialect

2023-03-09T15:29:18.729+05:00  INFO 45556 — [           main] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Utilizing JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]

2023-03-09T15:29:18.738+05:00  INFO 45556 — [           main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit ‘default’

***************************

APPLICATION FAILED TO START

***************************

Description:

Discipline employeeRepo in com.follow.springboot.fundamental.SpringBootPracticeApplication required a bean of kind ‘com.follow.springboot.repo.EmployeeRepo’ that would not be discovered.

The injection level has the next annotations:

– @org.springframework.beans.manufacturing unit.annotation.Autowired(required=true)

Motion:

Take into account defining a bean of kind ‘com.follow.springboot.repo.EmployeeRepo’ in your configuration.

Why this error – Take into account defining a bean of kind ‘package deal’ in your configuration?

It’s clear from the above error, that Spring Boot couldn’t discover a bean of kind EmployeeRepo (worker repository) inside the primary software. The above error is clear as a result of our software’s fundamental class is a part of a sub-package. 

Whereas, Spring Boot by default scans for entities, repositories, and controllers so long as they’re a part of the identical package deal or its baby package deal. Subsequently, it couldn’t acknowledge the entities, repositories, and controllers.  

For instance, there may very well be a typo as proven on this instance:

Tips on how to repair  Take into account defining a bean of kind ‘package deal’ in your configuration?

After recognizing the underlying drawback, now it’s time to unravel this challenge. There exist a few potential options. Just a few of them are listed beneath:

 Transfer the entity, controller, and repository courses into the primary package deal (the one containing Spring Boot’s fundamental class).

 Rename the package deal containing the primary class (make it the basis of the mission).

 Explicitly scan the entity, controller, and repository packages utilizing @EntityScan, @EnableJpaRepositories, and @ComponentScan annotation respectively.

Resolution 1:

Updating the primary class SpringBootPracticeApplication 

@SpringBootApplication

@EntityScan("com.follow.springboot.entity")

@EnableJpaRepositories("com.follow.springboot.repo")

@ComponentScan("com.follow.springboot.controller")

public class SpringBootPracticeApplication implements CommandLineRunner {



   @Autowired

   EmployeeRepo employeeRepo;



   public static void fundamental(String[] args) {

      SpringApplication.run(SpringBootPracticeApplication.class, args);

   }



   @Override

   public void run(String... args) throws Exception {

      Worker worker = new Worker();

      worker.setName("Muhammad");

      worker.setAge(25);

      worker.setSalary(10000);

      worker.setQualification("BE");



      

      employeeRepo.save(worker); 

   }

}

Resolution 2: Important software at root package deal of your mission.

├── fundamental

│   ├── java

│   │   └── com

│   │       └── follow

│   │           └── springboot

│   │               ├── controller

│   │               │   └── EmployeeController.java

│   │               ├── entity

│   │               │   └── Worker.java

│   │               ├── repo

│   │               │   └── EmployeeRepo.java

│   │               ├── service

│   │               └── SpringBootPracticeApplication.java

│   └── sources

│       ├── software.properties

│       ├── static

│       └── templates

└── take a look at

    └── java

        └── com

            └── follow

                └── springboot

                    └── SpringBootPracticeApplicationTests.java

After following the above directions, the appliance began as anticipated. Beneath is the affirmation from tomcat (embedded server).

2023-03-09T20:17:49.626+05:00  

INFO 51304 — [main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat began on port(s): 8080 (http) with context path ‘

Conclusion

The article has lastly come to an in depth. We’ve got targeting the spring boot error “think about defining a bean of kind package deal in your configuration”. On this brief article, we started the dialogue by comprehending the basis reason behind the error. Right here, we talk about potential errors and some fixes for them. I hope you’ll find this essay to be helpful.