Consider defining a bean of type package in your configuration Spring-Boot

Question

I am getting the following error                               APPLICATION FAILED TO START                              Description   Parameter 0 of method setApplicant in webService controller RequestController required a bean of type  com service applicant Applicant  that could not be found    Action   Consider defining a bean of type  com service applicant Applicant  in your configuration    I have never seen this error before but it s odd that the  Autowire is not working  Here is the project structure   Applicant Interface  public interface Applicant        TApplicant findBySSN String ssn  throws ServletException       void deleteByssn String ssn  throws ServletException       void createApplicant TApplicant tApplicant  throws ServletException       void updateApplicant TApplicant tApplicant  throws ServletException       List lt TApplicant gt  getAllApplicants   throws ServletException      ApplicantImpl   Service  Transactional public class ApplicantImpl implements Applicant    private static Log log   LogFactory getLog ApplicantImpl class        private TApplicantRepository applicantRepo    Override     public List lt TApplicant gt  getAllApplicants   throws ServletException            List lt TApplicant gt  applicantList   applicantRepo findAll             return applicantList            Now I should be able to just Autowire Applicant and be able to access  however in this case it is not working when I call it in my  RestController    RestController public class RequestController extends LoggingAware        private Applicant applicant        Autowired     public void setApplicant Applicant applicant           this applicant   applicant              RequestMapping value      method   RequestMethod GET      public String helloWorld              try               List lt TApplicant gt  applicantList   applicant getAllApplicants                 for  TApplicant tApplicant   applicantList                   System out println  Name    tApplicant getIndivName     SSN   tApplicant getIndSsn                                return  home                     catch  ServletException e                e printStackTrace                       return  error              ------------------------UPDATE 1-----------------------  I added    SpringBootApplication  ComponentScan  module-service   public class WebServiceApplication extends SpringBootServletInitializer         Override protected SpringApplicationBuilder configure SpringApplicationBuilder builder            return builder sources WebServiceApplication class              public static void main String   args            SpringApplication run WebServiceApplication class  args              and the error went away but nothing happened  However when I commented out everything dealing with Applicant in the RestController prior to adding  ComponentScan   I was able to return a string the UI  thus meaning my RestController was working  now it is being skipped  I ugly Whitelabel Error Page now   ---------------------UPDATE 2------------------------------  I added the base package of the bean it was complaining about  Error reads                               APPLICATION FAILED TO START                              Description   Parameter 0 of method setApplicantRepo in com service applicant ApplicantImpl required a bean of type  com delivery service request repository TApplicantRepository  that could not be found    Action   Consider defining a bean of type  com delivery request request repository TApplicantRepository  in your configuration    I added  ComponentScan   SpringBootApplication  ComponentScan   com delivery service   com delivery request    public class WebServiceApplication extends SpringBootServletInitializer         Override protected SpringApplicationBuilder configure SpringApplicationBuilder builder            return builder sources WebServiceApplication class              public static void main String   args            SpringApplication run WebServiceApplication class  args              ----------------------------Update 3----------------------  adding    SpringBootApplication  ComponentScan  com   public class WebServiceApplication extends SpringBootServletInitializer     still is complaining about my ApplicantImpl class which  Autowires my repo TApplicantRepository into it

User · Answer

Adding Spring Boot Data JPA Starter dependency solved the issue for me.

Maven

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-data-jpa</artifactId>
    <version>2.2.6.RELEASE</version>
</dependency>

Gradle

compile group: 'org.springframework.boot', name: 'spring-boot-starter-data-jpa', version: '2.2.6.RELEASE'

Or you can go directly here

User · Answer

There is a chance that you are trying to  autowired an interface before implement the interface   example solution          HomeController java       class HomeController          Autowired       UserService userService                  ----------------------------------------------------------------------       UserService java        public interface UserService           User findByUsername String username                   -----------------------------------------------------------------------        UserServiceImpl java         Service      public class UserServiceImpl implements UserService            public User findByUsername String username               return userDao findByUsername username                                     lt i gt This is not italic lt  i gt   and  this is not a link  https   example com

User · Answer

I faced with familiar problem in my Maven multi-module project with Spring Boot 2  The problem was related to naming of my packages in sub Maven modules     SpringBootApplication incapsulate a lots of component like -  ComponentScan   EnableAutoConfiguration  jpa-repositories  json-serialization and so on  And he places  ComponentScan in com         space package  This part of packages com         space must be common for all modules   For fixing it    You should rename all module packages  Other words you had to have in all packages in all Maven modules - the same parent part  For example - com         space  Also you have to move your entry point to this package - com         space

User · Answer

My error was that I had included    lt dependency gt       lt groupId gt org springframework data lt  groupId gt       lt artifactId gt spring-data-jpa lt  artifactId gt       lt version gt 2 2 5 RELEASE lt  version gt   lt  dependency gt    instead of    lt dependency gt       lt groupId gt org springframework boot lt  groupId gt       lt artifactId gt spring-boot-starter-data-jpa lt  artifactId gt   lt  dependency gt

User · Answer

This can also happen if you are using Lombok and you add the  RequiredArgsConstructor and  NonNull for fields but some of your fields are not to be injected in the constructor  This is only one of the possibilities to get the the same error      parameter 0 required a bean of type MissingBeanName that could not be found   In my case the error told me what Controller the problem was in  after removing  NonNull the application started fine

User · Answer

If your class dependency is managing by Spring then this issue may occur if we forgot to add default empty arg constructor inside our POJO class

User · Answer

Important  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     lt ------- THE IMPORTANT ONE public class Application    Side note  adding a  ComponentScan      beneath  SpringBootApplication is redundant  and your IDE should flag it as such  IntelliJ IDEA does  at least

User · Answer

You ll also get this error if you accidentally define the same bean in two different classes   That happened to me   The error message was misleading   When I removed the extra bean  the issue was resolved

User · Answer

There is a chance    You might be missing  Service   Repository annotation on your respective implementation classes

User · Answer

Remove annotation type configuration like  Service from the thread run method   Service   Component

User · Answer

Try configuring the project structure as given below  Put all the repo  service  packages in the child package of the main package  package com leisure moviemax     Parent package           SpringBootApplication  PropertySource value   quot classpath conf properties quot         public class MoviemaxApplication implements CommandLineRunner            package com leisure moviemax repo    child package   Repository public interface UsrRepository extends JpaRepository lt UserEntity String gt

User · Answer

Issue can also appeared when you use per example  EnableMongoRepositories YOUR MONGO REPOSITORIES PACKAGE  and later you renamed the package name or moved it in another place   Very often faced it within a multi-module maven project and spring boot

User · Answer

I sought online for an answer but it seems there is no one proper solution to my case   At the very beginning  everything works well as follows    Slf4j  Service  AllArgsConstructor onConstructor        Autowired   public class GroupService       private Repository repository      private Service service      Then I am trying to add a map to cache something and it becomes this     Slf4j  Service  AllArgsConstructor onConstructor        Autowired   public class GroupService       private Repository repository      private Service service      Map lt String  String gt  testMap      Boom   Description   Parameter 4 of constructor in   GroupService required a bean of type  java lang String  that could not be found    Action   Consider defining a bean of type  java lang String  in your configuration    I removed the  AllArgsConstructor onConstructor        Autowired   and add  Autowired for each repository and service except the Map lt String  String gt   It just works as before     Slf4j  Service public class SecurityGroupService        Autowired     private Repository repository       Autowired     private Service service      Map lt String  String gt  testMap      Hope this might be helpful

User · Answer

In my case I had a terrible mistake  I put  Service up to the service interface   To fix it  I put  Service on the implementation of service file and it worked for me

User · Answer

It worked for me after adding below annotation in application    ComponentScan   com seic deliveryautomation mapper     I was getting the below error       parameter 1 of constructor in required a bean of type mapper that could not be found

User · Answer

SpringBootApplication  MapperScan  com developer project mapper    public class Application       public static void main String   args            SpringApplication run Application class  args

User · Answer

Your Applicant class is not scanned it seems  By default all packages starting with the root as the class where you have put  SpringBootApplication will be scanned   suppose your main class   WebServiceApplication  is in  com service something   then all components that fall under  com service something  is scanned  and  com service applicant  will not be scanned   You can either restructure your packages such that  WebServiceApplication  falls under a root package and all other components becomes part of that root package  Or you can include  SpringBootApplication scanBasePackages   com service something   com service application    etc such that  ALL  components are scanned and initialized in the spring container   Update based on comment  If you have multiple modules that are being managed by maven gradle  all spring needs is the package to scan  You tell spring to scan  com module1  and you have another module which has its root package name as  com module2   those components wont be scanned  You can even tell spring to scan  com  which will then scan all components in  com module1   and  com module2

User · Answer

Moving the Springbootapplication application java  file to another package resolved the issue for me  Keep it separate from the controllers and repositories

User · Answer

For me worked a clean install on pom xml  right click on pom xml  expand Run As  select Maven build  set Goals to the command clean install  apply  gt  run  gt  close

User · Answer

If you use interface you can extends CrudRepository lt Applicant Long gt  with  Repository annotation

User · Answer

reminder that spring doesn t scan the world   it uses targeted scanning wich means everything under the package where springbootapplication is stored  therefore  this error  quot Consider defining a bean of type  package  in your configuration  Spring-Boot  quot  may appear because you have services interfaces in a different springbootapplication  package

User · Answer

If a bean is in the same package in which it is  Autowired  then it will never cause such an issue  However  beans are not accessible from different packages by default   To fix this issue follow these steps     Import following in your main class  import org springframework context annotation ComponentScan  add annotation over your main class      ComponentScan basePackages     your company domain package    public class SpringExampleApplication        public static void main String   args            SpringApplication run SpringExampleApplication class  args

User · Answer

It might be because the project has been broken down into different modules     SpringBootApplication  ComponentScan   com delivery request     EntityScan  com delivery domain    EnableJpaRepositories  com delivery repository   public class WebServiceApplication extends SpringBootServletInitializer

User · Answer

I think  you are missing the  Bean annotation in your RequestController   Add the Bean in your file  this solved my issue  I got this solution while I was learning Spring Boot from tutorialspoint  private Applicant applicant    Bean  public Applicant applicant          return new Applicant

User · Answer

Basically this happens when you have your Class Application in  another package   For example   com server  - Applicacion class   lt --this class have  ComponentScan  com server config  - MongoConfig class  com server repository  - UserRepository   I solve the problem with this in the Application class   SpringBootApplication  ComponentScan    com server    com server config     EnableMongoRepositories   com server repository      this fix the problem   Another less elegant way is to  put all the configuration classes in the same package

User · Answer

For me - using Spring Boot with MongoDB  the following was the Problem  In my POM xml I had   lt dependency gt       lt groupId gt org springframework boot lt  groupId gt       lt artifactId gt spring-starter-data-mongodb lt  artifactId gt   lt  dependency gt   but I needed the following       lt dependency gt           lt groupId gt org springframework boot lt  groupId gt           lt artifactId gt spring-boot-starter-data-mongodb lt  artifactId gt       lt  dependency gt    Short  Add  quot spring-boot-    quot  instead of only  quot spring-    quot

User · Answer

It might help somebody  I had the same problem  same error message  same everything  I tried solutions from other answers  didn t help until I realised that the bean I am using has the same name as the one that is actually been autowired  It happened in the midst of refactor  thus I had to rename the class  which resulted positively  Cheers

User · Answer

To fix errors like   Consider defining a bean of type  package  in your configuration Not a managed type  It happened to me that the LocalContainerEntityManagerFactoryBean class did not have the setPackagesToScan method  Then I proceeded to use the  EntityScan annotation which doesn t work correctly  Later I could find the method setPackagesToScan   but in another module  so the problem came from the dependency which did not have this method because it was an old version  This method can be found in the spring-data-jpa or spring-orm dependency of updated versions  From  implementation  quot org springframework quot    quot spring-orm quot    quot 2 5 1 quot     To  implementation  quot org springframework quot    quot spring-orm quot    quot 5 2 9 RELEASE quot    Or to  implementation  quot org springframework data quot    quot spring-data-jpa quot    quot 2 3 4 RELEASE quot    In addition  it was not necessary to add other annotations other than that of  SprintBootApplication   SpringBootApplication open class MoebiusApplication   SpringBootServletInitializer     Bean open fun entityManagerFactory     LocalContainerEntityManagerFactoryBean       val em   LocalContainerEntityManagerFactoryBean       em dataSource   dataSource       em setPackagesToScan  quot app mobius domain entity quot               GL Source

User · Answer

I think you can make it simplified by annotated your repository with  Repository  then it will be enabled automatically by Spring Framework

User · Answer

In my case these two options worked    in    ComponentScan    myapp    myapp resources   myapp services    include also the package which holds the Application class in the list  or Simply add  EnableAutoConfiguration  it automatically recognizes all the spring beans

User · Answer

I had a case where i need to inject RestTemplate into a service class  However  the RestTemplate cannot be picked up by the service class  What I did is to create a wrapper class under the same package as main application and mark the wrapper as Component and autowire this component in the service class  Problem solved  hope it also works for you

User · Answer

check the base package name If the package has different modules that are not prefixed with base package name

User · Answer

I faced the same issue  Mongo DB repository was identified by Spring boot  but it was not creating Bean for a repository interface that extended the mongo repository   The issue in my case was incorrect version specification in maven pom for  spring   mango   I have changed the artifact s group id and it all worked like magic  no annotations needed as spring boot took care of everything    During my problem resolution  I was all over web searching for solutions and realized that this problem is actually project configuration related  anyone facing this issue should first check their project setup and enable debug from spring to get more details on failure and pay close attention to where exactly in the process  the creation has failed

User · Answer

This can happen if the  Service class is marked abstract

User · Answer

Configuration annotation will just solve the error

User · Answer

In my case this error appear because my import was wrong  for example  using spring  the import automatically appear   import org jvnet hk2 annotations Service    but i needed   import org springframework stereotype Service

[java] Consider defining a bean of type 'package' in your configuration [Spring-Boot]

Examples related to java

Examples related to spring-boot