No Spring WebApplicationInitializer types detected on classpath

Question

My Eclipse project is suddenly no longer deploying properly   I can t trace it to any particular change I ve made to the environment   I have tested with multiple source-controlled projects and they are all behaving the same way   May 01  2013 12 00 45 PM org apache catalina core AprLifecycleListener init INFO  The APR based Apache Tomcat Native library which allows optimal performance in     production environments was not found on the java library path  C  Program Files    x86  Java jdk1 7 0 11 bin C  Windows Sun Java bin C  Windows system32 C  Windows C  Program Files  x86  NVIDIA     Corporation PhysX Common C  Windows system32 C  Windows C  Windows System32 Wbem C  Windows  System32 WindowsPowerShell v1 0    May 01  2013 12 00 45 PM org apache tomcat util digester SetPropertiesRule begin WARNING   SetPropertiesRule  Server Service Engine Host Context  Setting property  source  to  org eclipse jst jee server fismacm  did not find a matching property  May 01  2013 12 00 45 PM org apache coyote AbstractProtocol init INFO  Initializing ProtocolHandler   http-bio-8080   May 01  2013 12 00 45 PM org apache coyote AbstractProtocol init INFO  Initializing ProtocolHandler   ajp-bio-8009   May 01  2013 12 00 45 PM org apache catalina startup Catalina load INFO  Initialization processed in 296 ms May 01  2013 12 00 45 PM org apache catalina core StandardService startInternal INFO  Starting service Catalina May 01  2013 12 00 45 PM org apache catalina core StandardEngine startInternal INFO  Starting Servlet Engine  Apache Tomcat 7 0 35 May 01  2013 12 00 46 PM org apache catalina core ApplicationContext log INFO  No Spring WebApplicationInitializer types detected on classpath May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl core is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl sql rt is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jsp jstl sql is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl core rt is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jsp jstl core is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jsp jstl functions is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl fmt is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   jakarta apache org taglibs standard permittedTaglibs is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl xml is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   jakarta apache org taglibs standard scriptfree is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl fmt rt is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jsp jstl fmt is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jsp jstl xml is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl xml rt is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   java sun com jstl sql is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   www springframework org tags form is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   www springframework org tags is already defined May 01  2013 12 00 48 PM org apache catalina startup TaglibUriRule body INFO  TLD skipped  URI  http   www springframework org security tags is already defined May 01  2013 12 00 48 PM org apache catalina core ApplicationContext log INFO  No Spring WebApplicationInitializer types detected on classpath May 01  2013 12 00 48 PM org apache catalina core ApplicationContext log INFO  No Spring WebApplicationInitializer types detected on classpath May 01  2013 12 00 48 PM org apache catalina core ApplicationContext log INFO  Set web app root system property   webapp root         X  workspace  metadata  plugins org eclipse wst server core tmp0 wtpwebapps fismacm   May 01  2013 12 00 48 PM org apache catalina core ApplicationContext log INFO  Initializing log4j from  X  workspace  metadata  plugins org eclipse wst server core tmp0 wtpwebapps fismacm WEB-    INF log4j properties  May 01  2013 12 00 48 PM org apache catalina core ApplicationContext log INFO  Initializing Spring root WebApplicationContext SLF4J  Failed to load class  org slf4j impl StaticLoggerBinder   SLF4J  Defaulting to no-operation  NOP  logger implementation SLF4J  See http   www slf4j org codes html StaticLoggerBinder for further details  May 01  2013 12 00 49 PM org apache coyote AbstractProtocol start INFO  Starting ProtocolHandler   http-bio-8080   May 01  2013 12 00 49 PM org apache coyote AbstractProtocol start INFO  Starting ProtocolHandler   ajp-bio-8009   May 01  2013 12 00 49 PM org apache catalina startup Catalina start INFO  Server startup in 3898 ms   This seems like the key component   INFO  No Spring WebApplicationInitializer types detected on classpath     I ve tried cleaning the projects  redefining the servers  and even creating whole new workspaces   I ve clearly missed the mark   Any tips on getting this cleaned up would be greatly appreciated

User · Answer

xml was not in the WEB-INF folder  thats why i was getting this error  make sure that web xml and xxx-servlet xml is inside WEB INF folder and not in the webapp folder

User · Answer

I got a silly error it took me an embarrassingly long to solve     Check out my pom xml        lt  xml version  1 0  encoding  UTF-8   gt   lt project xmlns  http   maven apache org POM 4 0 0  xmlns xsi  http   www w3 org 2001 XMLSchema-instance  xsi schemaLocation  http   maven apache org POM 4 0 0 http   maven apache org xsd maven-4 0 0 xsd  gt   lt modelVersion gt 4 0 0 lt  modelVersion gt    lt groupId gt com outbottle lt  groupId gt   lt artifactId gt PersonalDetailsMVC lt  artifactId gt   lt version gt 1 0-SNAPSHOT lt  version gt   lt packaging gt war lt  packaging gt    lt name gt PersonalDetailsMVC lt  name gt    lt properties gt       lt endorsed dir gt   project build directory  endorsed lt  endorsed dir gt       lt project build sourceEncoding gt UTF-8 lt  project build sourceEncoding gt       lt spring version gt 4 0 1 RELEASE lt  spring version gt       lt jstl version gt 1 2 lt  jstl version gt       lt javax servlet version gt 3 0 1 lt  javax servlet version gt   lt  properties gt    lt dependencies gt       lt dependency gt           lt groupId gt javax lt  groupId gt           lt artifactId gt javaee-web-api lt  artifactId gt           lt version gt 7 0 lt  version gt           lt scope gt provided lt  scope gt       lt  dependency gt        lt dependency gt           lt groupId gt org springframework lt  groupId gt           lt artifactId gt spring-core lt  artifactId gt           lt version gt   spring version  lt  version gt       lt  dependency gt        lt dependency gt           lt groupId gt org springframework lt  groupId gt           lt artifactId gt spring-web lt  artifactId gt           lt version gt   spring version  lt  version gt       lt  dependency gt        lt dependency gt           lt groupId gt org springframework lt  groupId gt           lt artifactId gt spring-webmvc lt  artifactId gt           lt version gt   spring version  lt  version gt       lt  dependency gt        lt dependency gt           lt groupId gt javax servlet lt  groupId gt           lt artifactId gt javax servlet-api lt  artifactId gt           lt version gt   javax servlet version  lt  version gt           lt scope gt provided lt  scope gt       lt  dependency gt        lt dependency gt           lt groupId gt jstl lt  groupId gt           lt artifactId gt jstl lt  artifactId gt           lt version gt   jstl version  lt  version gt       lt  dependency gt    lt  dependencies gt    lt build gt       lt plugins gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-compiler-plugin lt  artifactId gt               lt version gt 3 1 lt  version gt               lt configuration gt                   lt source gt 1 8 lt  source gt                   lt target gt 1 8 lt  target gt                   lt compilerArguments gt                       lt endorseddirs gt   endorsed dir  lt  endorseddirs gt                   lt  compilerArguments gt               lt  configuration gt           lt  plugin gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-war-plugin lt  artifactId gt               lt version gt 2 3 lt  version gt               lt configuration gt                   lt failOnMissingWebXml gt false lt  failOnMissingWebXml gt               lt  configuration gt           lt  plugin gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-dependency-plugin lt  artifactId gt               lt version gt 2 6 lt  version gt               lt executions gt                   lt execution gt                       lt phase gt validate lt  phase gt                       lt goals gt                           lt goal gt copy lt  goal gt                       lt  goals gt                       lt configuration gt                           lt outputDirectory gt   endorsed dir  lt  outputDirectory gt                           lt silent gt true lt  silent gt                           lt artifactItems gt                               lt artifactItem gt                                   lt groupId gt javax lt  groupId gt                                   lt artifactId gt javaee-endorsed-api lt  artifactId gt                                   lt version gt 7 0 lt  version gt                                   lt type gt jar lt  type gt                               lt  artifactItem gt                           lt  artifactItems gt                       lt  configuration gt                   lt  execution gt               lt  executions gt           lt  plugin gt       lt  plugins gt   lt  build gt         Problem was my package name  It MUST be  com outbottle   then config controllers model etc  for it to work  As you can see above  I used Maven  for the first time   Spring  1 8 JDK and nearly had a stroke debugging this issue  All running on Glassfish  Tomcat is ok too for the above pom config   That said  I m all happy with myself now and know Maven and Spring much better for the next step of my Spring learning curve  Hoping this helps you also

User · Answer

I spent my whole day today investigating this problem and none of the answers helped  Here is my scenario  The WebApplicationInitializer types in my case are inside jar files  we have a multi-module gradle web project where each module is packaged as a jar and included in the web artifact  The problem is that Apache tomcat s classloader is not looking for the implementations of WebApplicationIntializer in WEB-INF lib instead its looking for those types directly under WEB-INF classes folder    Here is what I ended up doing for anyone who faces this problem in future    I implemented a ServletContainerInitializer myself and added that class name to META-INF services javax servlet ServletContainerInitializer  In the implementation  I copied the code from SpringServletContainerIntializer and used reflections to find the classes implementing a CustomWebApplicationInitializer interface  I did not make use of spring s WebApplicationInitializer interface to avoid any conflicts  Basically I have the same contract as WebApplicationInitializer with a different name  Now on startup  my container initializer is called and I delegated the call to all my CustomWebApplicationInitializers   Based on my search I also found that the loader used for tomcat can be updated to have it search in WEB-INF lib but I have little control over the tomcat I deploy my app to so went with the above solution  Hope this helps someone

User · Answer

This turned out to be a stupid error   My log4j wasn t configured to capture my error output   I was throwing configuration errors in the background and once I fixed those I was good to go and my request mappings worked fine

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 spent hours on this  and the solution was    Stop Tomcat  Project  menu -  Clean -  Clean all projects Servers tab -  Tomcat -  Right click -  Clean    Right click on project -  Run as -  Run on server

User · Answer

Watch out if you are using Maven  Your folder s structure must be right   When using Maven  the WEB-INF directory must be inside webapp   src main webapp WEB-INF

User · Answer

WebApplicationInitializer is an interface you can implement in one of your classes  At startup Spring is scanning for this classes  as long as you are using servlet spec 3 and have a metadata-complete  false  attribute in your web xml  But that doesn t seem to be the problem  The only error I can figure out is the missing slf4j-log4j12 jar

User · Answer

tomcat-maven-plugin in test  Tomcat usually does not add classes in src test java to the classpath  They are missing if you run tomcat in scope test  To order tomcat to respect classes in test  use -Dmaven tomcat useTestClasspath true or add    lt properties gt      lt maven tomcat useTestClasspath gt true lt  maven tomcat useTestClasspath gt   lt  properties gt    To your pom xml

User · Answer

INFO  No Spring WebApplicationInitializer types detected on classpath   Can also show up if you re using Maven with Eclipse and deploying your WAR using    Eclipse  Kepler  with M2    right-click on your project  -  Run As -  Run on Server  It s down to the generation and deletion of the m2e-wtp folder and contents   Make sure  Maven Archive generated files under the build directory is checked   Under   Window -  preferences -  Maven -  Java EE Integration   Then   Use M2  to do your build  i e  the usual Clean -  package or Install etc     If  Project -  Build Automatically  is not selected  You can force the  m2e-wtp folder and contents  generation by doing     right-click on your project  -  Maven -  Update Project      Note  make sure the  Clean Projects  option is un-selected  Otherwise the contents of target classes will be deleted and you re back to square one   Also when    Project -  Build Automatically  is selected the  m2e-wtp folder and contents  is generated  or  Project -  Build All   or   right-click on project  -  Build Project

User · Answer

In my case it also turned into a multi-hour debugging session  Trying to set up a more verbose logging turned out to be completely futile because the problem was that my application did not even start  Here s my context xml   lt  xml version  1 0  encoding  utf-8   gt   lt Context path  quot  rc2 quot  docBase  quot rc2 quot  antiResourceLocking  quot false quot   gt       lt JarScanner gt           lt JarScanFilter             tldScan  quot spring-webmvc  jar  spring-security-taglibs  jar  jakarta servlet jsp jstl  jar quot              tldSkip  quot   jar quot               lt  -- my-own-app  jar on the following line was missing  -- gt              pluggabilityScan  quot   tomcat util scan StandardJarScanFilter jarsToScan   my-own-app  jar quot              pluggabilitySkip  quot   jar quot   gt       lt  JarScanner gt   lt  Context gt   The problem was that to speed up the application startup  I started skipping scanning of many JARs  unfortunately including my own application

User · Answer

STS has a metadata folder under its workspace  You will see the actual error in  log file under C  Users firstname lastname Documents workspace-sts-3 9 2 RELEASE metadata

User · Answer

I faced this problem and finally resolved  Please make sure that your web xml and Servlet xml file should present in web inf folder    Also Please add spring jars into Web Deployment assembly in project properties  We might missed out this when setting up the project from beginning

[spring] No Spring WebApplicationInitializer types detected on classpath

Examples related to spring

Examples related to model-view-controller

Examples related to tomcat

Examples related to servlets

Examples related to spring-mvc