INFO No Spring WebApplicationInitializer types detected on classpath

Question

I have a spring project that runs fine on my tomcat7 server when I deploy from eclipse  Run As    Run on server  In the eclipse tab  Servers  I see   Servers  Tomcat v7 0 Server at localhost  Started  Synchronized     my project  Synchronized       spring-web-3 2 4-RELEASE jar   My project    does not use web xml  I use javaconf   annotations  does not use maven  I use a User Library   I see that the project is in    srv applications workspace  metadata  plugins org eclipse wst server core tmp0   And  I also see the folders  conf logs temp webapps work wtpwebapps  I confirm that all runs fine on my tomcat7 server when I deploy from eclipse   In eclipse console I get   Apr 08  2014 3 26 59 PM org apache tomcat util digester SetPropertiesRule begin WARNING   SetPropertiesRule  Server Service Engine Host Context  Setting property  source  to  org eclipse jst j2ee server my project  did not find a matching property  Apr 08  2014 3 27 00 PM org apache coyote AbstractProtocol init INFO  Initializing ProtocolHandler   http-bio-8888   Apr 08  2014 3 27 00 PM org apache coyote AbstractProtocol init INFO  Initializing ProtocolHandler   http-bio-8843   Apr 08  2014 3 27 01 PM org apache catalina startup Catalina load INFO  Initialization processed in 3215 ms Apr 08  2014 3 27 01 PM org apache catalina core StandardService startInternal INFO  Starting service Catalina Apr 08  2014 3 27 01 PM org apache catalina core StandardEngine startInternal INFO  Starting Servlet Engine  Apache Tomcat 7 0 26 Apr 08  2014 3 27 11 PM org apache catalina core ApplicationContext log INFO  Spring WebApplicationInitializers detected on classpath   my project web context WebApplicationInitializer 3599e94c  Apr 08  2014 3 27 12 PM org apache catalina core ApplicationContext log INFO  Initializing Spring root WebApplicationContext Apr 08  2014 3 27 24 PM org apache catalina core ApplicationContext log INFO  Initializing Spring FrameworkServlet  dispatcher  Apr 08  2014 3 27 24 PM org apache coyote AbstractProtocol start INFO  Starting ProtocolHandler   http-bio-8888   Apr 08  2014 3 27 24 PM org apache coyote AbstractProtocol start INFO  Starting ProtocolHandler   http-bio-8843   Apr 08  2014 3 27 24 PM org apache catalina startup Catalina start INFO  Server startup in 23821 ms   Now  The problem It is when I deploy the same app  using a file  war  in the same tomcat7 server  var lib tomcat7 webapps  I can open the my initial page web BUT without data   I see in the log   INFO  No Spring WebApplicationInitializer types detected on classpath   When I restart tomcat7 I get in the log file   INFO  Destroying ProtocolHandler   http-bio-8843   Apr 8  2014 3 25 30 PM org apache tomcat util digester SetPropertiesRule begin WARNING   SetPropertiesRule  Server Service Engine Host Context  Setting property  source  to  org eclipse jst j2ee server my project  did not find a matching property  Apr 8  2014 3 25 30 PM org apache coyote AbstractProtocol init INFO  Initializing ProtocolHandler   http-bio-8888   Apr 8  2014 3 25 31 PM org apache coyote AbstractProtocol init INFO  Initializing ProtocolHandler   http-bio-8843   Apr 8  2014 3 25 31 PM org apache catalina startup Catalina load INFO  Initialization processed in 1664 ms Apr 8  2014 3 25 31 PM org apache catalina core StandardService startInternal INFO  Starting service Catalina Apr 8  2014 3 25 31 PM org apache catalina core StandardEngine startInternal INFO  Starting Servlet Engine  Apache Tomcat 7 0 26 Apr 8  2014 3 25 38 PM org apache coyote AbstractProtocol start INFO  Starting ProtocolHandler   http-bio-8888   Apr 8  2014 3 25 38 PM org apache coyote AbstractProtocol start INFO  Starting ProtocolHandler   http-bio-8843   Apr 8  2014 3 25 38 PM org apache catalina startup Catalina start INFO  Server startup in 7576 ms

User · Answer

I had similar problem with Tomcat 8 embedded in java7 application.

When I launched Tomcat in my application, it worked. But when I launched it through Maven for integration test purpose, I got this error : "No Spring WebApplicationInitializer types detected on classpath".

I fixed it by upgrading org.apache.tomcat.embed:tomcat-embed-* dependencies from version 8.0.29 to 8.0.47.

User · Answer

For eclipse users  solution is simple just change the nature of project Spring Tools- add spring project nature  done

User · Answer

I also had the same problem  My maven had tomcat7 plugin but the JRE environment was 1 6  I changed my tomcat7 to tomcat6 and the error was gone

User · Answer

I had this info message  No Spring WebApplicationInitializer types detected on classpath  while deploying a WAR with spring integration beans in WebLogic server  Actually  I could observe that the servlet URL returned 404 Not Found and beside that info message with a negative tone  No Spring    etc  in Server logs  nothing else was seemingly in error in my spring config  no build or deployment errors  no complaints  Indeed  I suspected that the beans xml  spring context XML  was actually not picked up at all and that was bound to the very specific organizing of artefacts in Oracle s jDeveloper  The solution is to play carefully with the  contributors  and  filters  for the WEB-INF classes category when you edit your deployment profile under the  deployment  topic in project properties   Precisely  I would advise to name your spring context by the jDeveloper default  beans xml  and place it side by side to the WEB-INF subdirectory itself  under your web Apllication source path  e g  like  lt    your project path  public html    Then in the WEB-INF classes category  when editing the deployment profile  your can check the Project HTML root directory in the  contributor  list  and then select the beans xml in filters  and then ensure your web xml features a context-param value like classpath beans xml   Once that was fixed  I was able to progress and after some more bean config changes and implementations  the message  No Spring WebApplicationInitializer types detected on classpath  came back  Actually  I did not notice when and why exactly it came back  This second time  I added a   public class HttpGatewayInit implements WebApplicationInitializer           which implements empty inherited methods  and the whole application works fine      If you feel that java EE development has been getting a bit too crazy with cascades of XML configuration files  some edited manually  others through wizards  intepreted by cascades of variant initializers  let me insist that I fully share your point

User · Answer

My silly reason was  Build Automatically was disabled

User · Answer

lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-compiler-plugin lt  artifactId gt                 lt configuration gt           lt source gt 1 8 lt  source gt           lt target gt 1 8 lt  target gt       lt  configuration gt    lt  plugin gt    This is the important plugin that should be in pom xml  I spent my two days debugging and researching  This was the solution  This is Apache plugin to tell maven to use the the given Compiler

User · Answer

This is common error  make sure that your file war is built correctly  Just open  war file and check that your WebApplicationInitializer is there

User · Answer

I found the error  I have a library that it was built using jdk 1 6  The Spring main controller and components are in this library  And how I use jdk 1 7  It does not find the classes built in 1 6    The solution was built all using  compiler compliance level  1 7  and  Generated  class files compatibility  1 6    Source compatibility  1 6    I setup this option in Eclipse   Preferences Java Compiler   Thanks everybody

User · Answer

Make sure that your log4j is configured correctly  there s probably an exception that is being thrown  but you re only seeing half of the picture   Please see https   stackoverflow com a 16817018 1249304

[java] INFO: No Spring WebApplicationInitializer types detected on classpath

Examples related to java

Examples related to spring

Examples related to spring-mvc

Examples related to tomcat7