0

I have a Spring MVC application, using Hibernate for my entities persistence management. I am able to build, deploy and run it on some application server such as glashfish or tomcat, all is fine.

Now, I want to convert it into a Spring Boot application. I added the following class:

@SpringBootApplication
public class Application extends SpringBootServletInitializer {

    @Override
    protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
        return application.sources(Application.class);
    }

    public static void main(String[] args) {
        ConfigurableApplicationContext context = 
                            SpringApplication.run(Application.class, args);
    }
}

and added the spring-boot, spring-boot-autoconfigure, and spring-boot-starter-tomcat dependencies to my pom.

Alas, when trying to run the application, I get the following error:

BeanCurrentlyInCreationException: Error creating bean with name
'MyClassDAO': Bean with name 'MyClassDAO' has been injected into 
other beans [MyOtherClassDAO] in its raw version as part of a circular
reference, but has eventually been wrapped. This means that said other
beans do not use the final version of the bean. This is often the result
of over-eager type matching - consider using 'getBeanNamesOfType' with 
the 'allowEagerInit' flag turned off, for example.

I don't know how to use 'getBeanNamesOfType' and set the allowEagerInit off (I do not use XML configuration). Of course, I'm not sure this would solve my issue anyway.

Any ideas on how I can fix this?

nmpg
  • 561
  • 2
  • 10
  • 24
  • http://stackoverflow.com/questions/10008714/requested-bean-is-currently-in-creation-is-there-an-unresolvable-circular-refer – kamokaze Oct 09 '16 at 12:08
  • Thank you @kamokaze. The setter injection approach did not really work for me, but using some PostConstruct's saved the day. – nmpg Oct 09 '16 at 15:28
  • 1
    Still don't know why it works with no issue on Spring MVC based app, and crashed in Spring Boot though. – nmpg Oct 09 '16 at 15:29
  • Did you package to the war file? Here are some [steps](https://docs.spring.io/spring-boot/docs/1.4.1.RELEASE/reference/htmlsingle/#howto-create-a-deployable-war-file) – Liping Huang Oct 10 '16 at 06:08

1 Answers1

0

If it's really some intilization issue then i believe the you must be having your class in other package and due to some cache issues it doesn't include those classes in class path to scan in container so to do this manually you can put a annotation just below @springbootapllication is @EnableComponentScan("enter the package name of the class which is not initializing") also on that dao class put @service or @component annotation to let the application include then in container

Amit Mishra
  • 498
  • 5
  • 16