jar not loaded See Servlet Spec 2 3 section 9 7 2 Offending class javax servlet Servlet class

Question

I am running a Maven project which is also a dynamic web project  I have used all Spring libraries in Maven  I created web xml  but when I start my Tomcat 7 server I am getting the following message   INFO  validateJarFile C  Users mibvzd0 workspace  metadata  plugins  org eclipse wst server core tmp2 wtpwebapps hapi hl7 WEB-INF lib  servlet-api-2 4 jar  - jar not loaded  See Servlet Spec 2 3  section 9 7 2  Offending class  javax servlet Servlet class   I tried deleting the servlet from webapp lib  but it didn t work  Let me know what should be done in my case

User · Answer

The JAX-WS dependency library    jaxws-rt jar    is missing   Go here http   jax-ws java net   Download JAX-WS RI distribution  Unzip it and copy    jaxws-rt jar    to Tomcat library folder      TOMCAT  lib     Restart Tomcat

User · Answer

Exclusions and provided dependencies will not work in child projects   If you are using inheritance in Maven projects you must include this configuration on the parent pom xml file  You  will have a  lt parent gt     lt  parent gt  section in your pom xml if you are using inheritance  So you will have something like this in your parent pom xml    lt groupId gt some groupId lt  groupId gt   lt version gt 1 0 lt  version gt   lt artifactId gt someArtifactId lt  artifactId gt   lt packaging gt pom lt  packaging gt   lt modules gt       lt module gt child-module-1 lt  module gt       lt module gt child-module-2 lt  module gt   lt  modules gt   lt dependencies gt       lt dependency gt           lt groupId gt javax servlet lt  groupId gt           lt artifactId gt servlet-api lt  artifactId gt           lt version gt 2 5 lt  version gt           lt scope gt provided lt  scope gt       lt  dependency gt       lt dependency gt           lt groupId gt javax servlet jsp lt  groupId gt           lt artifactId gt jsp-api lt  artifactId gt           lt version gt 2 1 lt  version gt           lt scope gt provided lt  scope gt       lt  dependency gt   lt  dependencies gt

User · Answer

Maven Dependency Scope      provided   This is much like compile  but indicates you expect the JDK or a container to provide the dependency at runtime  For example    when building a web application for the Java Enterprise Edition  you   would set the dependency on the Servlet API and related Java EE APIs   to scope provided because the web container provides those classes    This scope is only available on the compilation and test classpath    and is not transitive

User · Answer

I ve been struggling with this issue and I ve tried numerous  solutions    However  in the end  the only one that worked and it actually took a few seconds to do it was to  delete and add back new server instance   Basically  I right clicked on my Tomcat server in Eclipse under Servers and deleted it  Next  I ve added a new Tomcat server  Cleaned and redeployed the application and I got rid of this error

User · Answer

Check Inside the Following Directory for the jar file el-api jar   C  apache-tomcat-7 0 39 lib el-api jar  if it exists then in this directory of your web application  WEB-INF lib el-api jar   the jar should be removed

User · Answer

when your URL pattern is wrong  this error may be occurred   eg  If you wrote  WebServlet  login    this error will be shown  The correct one is  WebServlet   login

User · Answer

You get this warning message when the servlet api jar file has already been loaded in the container and you try to load it once again from lib directory      The Servlet specs say you are not allowed to have servlet jar in   your webapps lib directory     Get rid of the warning message by simply removing servlet jar from your lib directory  If you don t find the jar in the lib directory scan for your build path and remove the jar      C  Program Files Apache Software Foundation Tomcat 7 0 webapps project WEB-INF lib   If you are running a maven project  change the javax servlet-api dependency to scope provided in you pom xml since the container already provided the servlet jar in itself

User · Answer

Typically when you see this message  it is benign  If it says  INFO  validateJarFile   lt webapp gt  WEB-INF lib servlet-api-2 5 jar  - jar not loaded   See Servlet Spec 2 3  section 9 7 2  Offending class  javax servlet Servlet class   It means it is ignoring your servlet-api-2 5 jar because tomcat already has a built-in version of that jar  so it isn t going to be using yours   Typically this doesn t cause an issue   If however it says WEB-INF lib my jar jar - jar not loaded   Offending class  javax servlet Servlet class  then what you can do  in my instance  it s a shaded jar  is run    mvn dependency tree  and discover that you have a transitive dependency on  something  that depends on a jar that is either servlet-api or something like it  ex  tomcat-servlet-api-9 0 0    So add an exclusion to that to your pom  ex   in my case  tomcat  in your case  probably the ones mentioned in the other answers      lt dependency gt               lt exclusions gt         lt exclusion gt           lt groupId gt org apache tomcat lt  groupId gt           lt artifactId gt tomcat-servlet lt  artifactId gt         lt  exclusion gt       lt  exclusions gt    lt  dependency gt

User · Answer

To fix it  set the scope to provided  This tells Maven use code servlet-api jar for compiling and testing only  but NOT include it in the WAR file  The deployed container will    provide    the servlet-api jar at runtime    lt dependency gt       lt groupId gt javax servlet lt  groupId gt       lt artifactId gt servlet-api lt  artifactId gt       lt version gt 2 5 lt  version gt       lt scope gt provided lt  scope gt   lt  dependency gt

User · Answer

The servlet API  jar file must not be embedded inside the webapp since  obviously  the container already has these classes in its classpath  it implements the interfaces contained in this jar   The dependency should be in the provided scope  rather than the default compile scope  in your Maven pom    lt dependency gt       lt groupId gt javax servlet lt  groupId gt       lt artifactId gt javax servlet-api lt  artifactId gt       lt version gt 3 1 0 lt  version gt       lt scope gt provided lt  scope gt   lt  dependency gt

User · Answer

You may find the following windows command line useful in tracking down the offending jar file   it creates an index of all the class files in all the jars in the folder   Execute from within the lib folder of your deployed app  then search the index txt file for the offending class   for  r  X in    jar  do  echo  X  amp  jar -tf  X   gt  gt  index txt

User · Answer

Remove servlet jar from source web-inf lib folder as it is available in tomcat lib folder then it works fine

[java] jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class

Examples related to java

Examples related to eclipse

Examples related to maven

Examples related to tomcat7