|Re: How to exclude Groovy plugin jars from Tomcat classpath [message #1220439 is a reply to message #1220138]
||Wed, 11 December 2013 17:51
| Larry Isaacs
Registered: July 2009
On 12/9/2013 11:34 PM, steve B wrote:|
> Downloaded the latest Tomcat and created a new runtime and server config
> in WTP but I got the LinkageError for "javax/servlet/ServletResponse".
> It seems that Maven/m2e is somehow involved in this because I don't get
> the error if I remove the elasticsearch dependency from the pom, this
> started happening only after adding that dependency. Looking at the
> dependency hierarchy when I view the pom in Eclipse, elasticsearch
> doesn't have a dependency on anything other than Lucene so its unclear
> why it has an effect on the server classpath.
If you look at the published webapp under
do you see "servlet-api" jar(s) included in its "WEB-INF/lib"?
While it is technically not correct to include a servlet-api jar in
WEB-INF/lib of a webapp, Tomcat tries to help out by ignoring the jar.
If this is occurring, you would see an INFO message in the console log
like the following:
INFO: validateJarFile(<path to jar>) - jar not loaded. See Servlet Spec
2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Are you seeing this?
Powered by FUDForum
. Page generated in 0.12044 seconds