tomcat发布基于jersey的WebService(三)
2009-11-16 19:24
411 查看
可恶的异常!
周末的一个下午都被这个异常给耽误了。哎
很奇怪的原因,之前的jersey测试都是基于myeclipse自带的tomcat进行部署调试的,未发现任何异常。这次我把jersey应用到以前做的project中,然后部署在我安装的tomcat6.0中,结果部署除了这么个异常!google也找不到任何解答。将jersey测试项目也部署到tomcat6.0中也出现这样的异常。但是部署在myeclipse自带的tomcat中就不出现这样的异常,深度不解~
就这样折腾了一个下午的时间~
第二天晚上又打开来调试,问题依旧,没办法登陆jersey官网看看,在guide中发现这样一句:
Non-maven developers require:
jersey-server.jar
,
jersey-core.jar
,
jsr311-api.jar
,
asm.jar
于是将jersey包精简到以上几个,去掉了几个client测试相关的jar和spring支持jar,还有一个jersey-multipart-1.1.2-ea.jar(问题就是个jar)。启动tomcat6,异常消失了。^_^
反复改变部署的jars,直接的方法就是把jersey-multipart-1.1.2-ea.jar去掉。其他的jar目前倒是没有产生影响。
哎,水平有限,我也总结不出个合理的解释,只能告诉大家以后jersey不要部署多余的jar!(好像之前也是参考某个blog建议把contribs和lib下的jar都复制过去)。有知道原因的没?各位。
周末的一个下午都被这个异常给耽误了。哎
严重: StandardWrapper.Throwable com.sun.jersey.spi.service.ServiceConfigurationError: jersey-server-components: A dependent class, org/jvnet/mimepull/MIMEParsingException, of the class com.sun.jersey.multipart.impl.MultiPartReader implementing the provider class java.lang.Object is not found. The provider implementation is ignored. at com.sun.jersey.spi.service.ServiceFinder.fail(ServiceFinder.java:388) at com.sun.jersey.spi.service.ServiceFinder.access$200(ServiceFinder.java:144) at com.sun.jersey.spi.service.ServiceFinder$LazyClassIterator.next(ServiceFinder.java:595) at com.sun.jersey.spi.service.ServiceFinder$LazyClassIterator.next(ServiceFinder.java:571) at com.sun.jersey.spi.service.ServiceFinder.toClassArray(ServiceFinder.java:374) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:437) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:420) at com.sun.jersey.spi.container.servlet.ServletContainer.initiate(ServletContainer.java:377) at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(ServletContainer.java:242) at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:466) at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:182) at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:281) at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:442) at javax.servlet.GenericServlet.init(GenericServlet.java:212) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4042) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4348) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 2009-11-16 19:19:19 org.apache.catalina.core.StandardContext loadOnStartup 严重: Servlet /jerseyWebServiceTest threw load() exception com.sun.jersey.spi.service.ServiceConfigurationError: jersey-server-components: A dependent class, org/jvnet/mimepull/MIMEParsingException, of the class com.sun.jersey.multipart.impl.MultiPartReader implementing the provider class java.lang.Object is not found. The provider implementation is ignored. at com.sun.jersey.spi.service.ServiceFinder.fail(ServiceFinder.java:388) at com.sun.jersey.spi.service.ServiceFinder.access$200(ServiceFinder.java:144) at com.sun.jersey.spi.service.ServiceFinder$LazyClassIterator.next(ServiceFinder.java:595) at com.sun.jersey.spi.service.ServiceFinder$LazyClassIterator.next(ServiceFinder.java:571) at com.sun.jersey.spi.service.ServiceFinder.toClassArray(ServiceFinder.java:374) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:437) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:420) at com.sun.jersey.spi.container.servlet.ServletContainer.initiate(ServletContainer.java:377) at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(ServletContainer.java:242) at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:466) at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:182) at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:281) at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:442) at javax.servlet.GenericServlet.init(GenericServlet.java:212) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4042) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4348) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
很奇怪的原因,之前的jersey测试都是基于myeclipse自带的tomcat进行部署调试的,未发现任何异常。这次我把jersey应用到以前做的project中,然后部署在我安装的tomcat6.0中,结果部署除了这么个异常!google也找不到任何解答。将jersey测试项目也部署到tomcat6.0中也出现这样的异常。但是部署在myeclipse自带的tomcat中就不出现这样的异常,深度不解~
就这样折腾了一个下午的时间~
第二天晚上又打开来调试,问题依旧,没办法登陆jersey官网看看,在guide中发现这样一句:
Non-maven developers require:
jersey-server.jar
,
jersey-core.jar
,
jsr311-api.jar
,
asm.jar
于是将jersey包精简到以上几个,去掉了几个client测试相关的jar和spring支持jar,还有一个jersey-multipart-1.1.2-ea.jar(问题就是个jar)。启动tomcat6,异常消失了。^_^
反复改变部署的jars,直接的方法就是把jersey-multipart-1.1.2-ea.jar去掉。其他的jar目前倒是没有产生影响。
哎,水平有限,我也总结不出个合理的解释,只能告诉大家以后jersey不要部署多余的jar!(好像之前也是参考某个blog建议把contribs和lib下的jar都复制过去)。有知道原因的没?各位。
相关文章推荐
- tomcat发布基于jersey的WebService(二)
- tomcat发布基于jersey的WebService
- tomcat发布基于jersey的WebService(一)
- 一个实例演示jersey框架实现RESTful风格的Webservice,并发布到Tomcat,以及客户端调用示范
- 验证发布到Tomcat的基于JAX-WS的Webservice的并发
- 无废话的基于axis2+tomcat架构webservice 的java 应用流程
- WebService -- Java 实现之 CXF ( 使用:Spring+CXF+Tomcat发布webService)
- jersey 基于tomcat web service 开发 restful service
- eclipse安装Axis2 +Tomcat的webservice发布
- 使用myEclipse,tomcat 和Axis发布webService
- WebService学习之旅(五)基于Apache Axis2发布第一个WebService
- 使用CXF发布基于maven的REST webservice接口
- CXF整合Spring通过tomcat发布webservice
- 在Eclipse中使用Jersey和Tomcat构建RESTful WebService及其调用
- JAX-WS在tomcat上发布Webservice
- 开发基于CXF的 RESTful WebService web 项目 webservice发布
- 基于Tomcat的自动构建和发布
- Webservice实践(七)CXF 与Spring结合+tomcat发布
- 基于JAVA中使用Axis发布/调用Webservice的方法详解
- MyEclipse8.5创建webService发布到Tomcat 6和weblogic