Maven集成Tomcat的小问题:“ XXX类 cannot be cast to javax.servlet.Servlet ”

maven集成tomcat,顺利跑起来,访问servlet报错,错误信息如下:

十二月 25, 2018 10:39:52 上午 org.apache.catalina.core.StandardWrapperValve invoke
严重: Allocate exception for servlet helloMaven
java.lang.ClassCastException: MavenLearnPackage.HelloMavenServlet cannot be cast to javax.servlet.Servlet
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1136)
	at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:857)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:136)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

事关servlet转换,先检测了相关类,未发现问题,想到查看pom文件里边对依赖包的配置,发现配置如下:

...
	<!-- 配置servlet api依赖 -->
	<!-- https://mvnrepository.com/artifact/javax.servlet/javax.servlet-api -->
	<dependency>
	    <groupId>javax.servlet</groupId>
	    <artifactId>javax.servlet-api</artifactId>
	    <version>3.1.0</version>
	</dependency>
...

    	<!-- tomcat插件配置 -->
    	<!-- https://mvnrepository.com/artifact/org.apache.tomcat.maven/common-tomcat-maven-plugin -->
		<plugin>
			<groupId>org.apache.tomcat.maven</groupId>
			<artifactId>tomcat7-maven-plugin</artifactId>
			<version>2.0</version>
			<configuration>
				<path>/</path>
				<port>8080</port>
				<uriEncoding>UTF-8</uriEncoding>
				<url>http://127.0.0.1</url>
				<server>tomcat7</server>
			</configuration>
		</plugin>
...

显然,访问相关servlet时,servlet相关包发生了冲突,更改servlet-api这个依赖包的依赖范围,访问成功。

顺便总结一下依赖范围scope:

compile:编译范围,此范围为默认依赖范围。编译范围的依赖会用在编译、测试、运行,由于运行时需要所以编译范围的依赖会被打包。

provided:provided依赖在编译和测试时需要,在运行时不需要。

runtime:runtime依赖在运行和测试系统的时候需要,但在编译的时候不需要。

test:test范围依赖 在编译和运行时都不需要,它们只有在测试编译和测试运行阶段可用。

system:system范围依赖与provided类似,必须显式的提供一个对于本地系统中JAR文件的路径。引用本机jar包,移植到其它机器后无法获取jar包。

猜你喜欢

转载自blog.csdn.net/txd2016_5_11/article/details/85244255