Tomcat無法在Eclipse中的Tomcat上部署我的servlet（NoClassDefFoundError）

在使用Java EE Eclipse（Juno）創建的Maven項目中，我有一個Hello Wolrd Servlet。 pom.xml中指定以下內容的依賴關係：Tomcat無法在Eclipse中的Tomcat上部署我的servlet（NoClassDefFoundError）

的junit
Tomcat的服務器的API

「運行方式>的Maven安裝」似乎運行精細和/目標輸出.war文件/。

這個.war部署（Apache應用程序管理器），並在使用tomcat 7.0.26-1ubuntu1.2（通過apt-get安裝）的其他機器上正常運行。

我配置了Eclipse（使用服務器視圖）以使用從tar.gz歸檔中提取的apache-tomcat-7.0.40安裝。它也運行正常使用「運行」>在服務器上運行「。現在

，如果我添加此到的Hello World的servlet：

PropertiesConfiguration config = new 
PropertiesConfiguration("config.properties");

和

import org.apache.commons.configuration.ConfigurationException; 
import org.apache.commons.configuration.PropertiesConfiguration;

，並添加以下的依賴，以我的pom.xml：

<dependency> 
    <groupId>commons-configuration</groupId> 
    <artifactId>commons-configuration</artifactId> 
    <version>1.9</version> 
</dependency>

它在遠程服務器上運行良好，但是在Eclipse中使用「運行方式」>「在服務器上運行」時，它會失敗，這對ef來說並不酷夠的開發&調試：

May 30, 2013 6:42:28 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: /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib 
May 30, 2013 6:42:28 PM org.apache.tomcat.util.digester.SetPropertiesRule begin 
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:proxy' did not find a matching property. 
May 30, 2013 6:42:28 PM org.apache.coyote.AbstractProtocol init 
INFO: Initializing ProtocolHandler ["http-bio-8080"] 
May 30, 2013 6:42:28 PM org.apache.coyote.AbstractProtocol init 
INFO: Initializing ProtocolHandler ["http-bio-5443"] 
May 30, 2013 6:42:28 PM org.apache.coyote.AbstractProtocol init 
INFO: Initializing ProtocolHandler ["ajp-bio-8009"] 
May 30, 2013 6:42:28 PM org.apache.catalina.startup.Catalina load 
INFO: Initialization processed in 561 ms 
May 30, 2013 6:42:28 PM org.apache.catalina.core.StandardService startInternal 
INFO: Starting service Catalina 
May 30, 2013 6:42:28 PM org.apache.catalina.core.StandardEngine startInternal 
INFO: Starting Servlet Engine: Apache Tomcat/7.0.40 
May 30, 2013 6:42:28 PM org.apache.catalina.core.ContainerBase startInternal 
SEVERE: A child container failed during start 
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/proxy]] 
    at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) 
    at java.util.concurrent.FutureTask.get(FutureTask.java:111) 
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123) 
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) 
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) 
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
    at java.lang.Thread.run(Thread.java:679) 
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/proxy]] 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) 
    ... 7 more 
Caused by: java.lang.NoClassDefFoundError: org/apache/commons/configuration/ConfigurationException 
    at java.lang.Class.getDeclaredFields0(Native Method) 
    at java.lang.Class.privateGetDeclaredFields(Class.java:2318) 
    at java.lang.Class.getDeclaredFields(Class.java:1762) 
    at org.apache.catalina.util.Introspection.getDeclaredFields(Introspection.java:106) 
    at org.apache.catalina.startup.WebAnnotationSet.loadFieldsAnnotation(WebAnnotationSet.java:261) 
    at org.apache.catalina.startup.WebAnnotationSet.loadApplicationServletAnnotations(WebAnnotationSet.java:140) 
    at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:67) 
    at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:405) 
    at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:881) 
    at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369) 
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) 
    at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) 
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5269) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    ... 7 more 
Caused by: java.lang.ClassNotFoundException: org.apache.commons.configuration.ConfigurationException 
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714) 
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559) 
    ... 21 more 
May 30, 2013 6:42:28 PM org.apache.catalina.core.ContainerBase startInternal 
SEVERE: A child container failed during start 
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]] 
    at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) 
    at java.util.concurrent.FutureTask.get(FutureTask.java:111) 
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123) 
    at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:302) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    at org.apache.catalina.startup.Catalina.start(Catalina.java:684) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
    at java.lang.reflect.Method.invoke(Method.java:616) 
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322) 
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:456) 
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]] 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) 
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) 
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) 
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
    at java.lang.Thread.run(Thread.java:679) 
Caused by: org.apache.catalina.LifecycleException: A child container failed during start 
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1131) 
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    ... 7 more 
May 30, 2013 6:42:28 PM org.apache.catalina.startup.Catalina start 
SEVERE: Catalina.start: 
org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]] 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) 
    at org.apache.catalina.startup.Catalina.start(Catalina.java:684) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
    at java.lang.reflect.Method.invoke(Method.java:616) 
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322) 
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:456) 
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]] 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) 
    at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    ... 7 more 
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina]] 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) 
    at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    ... 9 more 
Caused by: org.apache.catalina.LifecycleException: A child container failed during start 
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1131) 
    at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:302) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 
    ... 11 more 
May 30, 2013 6:42:28 PM org.apache.catalina.startup.Catalina start 
INFO: Server startup in 239 ms

讀了一堆的帖子，我發現了一種方法，使其工作在做「屬性>部署大會>添加> Java構建路徑條目> Maven依賴」，但Maven的重置此設置一個「Maven>更新項目」。

是否可以在pom.xml中定義適當的設置以避免此問題？

額外信息：我正在使用maven-compiler-plugin和maven-war-plugin。（可能是走錯了路！）

來源

2013-05-30 jeff

（可能）無關，但你不能部署你自己的servlet-api;你有沒有把它定義爲你的pom中「提供」的？ –

感謝您的提示。我更新爲「提供」，它仍然在遠端服務器上運行良好，並且在集成的eclipse上失敗。我剛剛在「Properties> Deployment Assembly> Add> Java Build Path Entries> Maven Dependencies」之前和之後做了項目差異，結果如下： /project /。類路徑是不同的： '<\t \t \t <屬性名= 「org.eclipse.jst.component.dependency」值= 「/ WEB-INF/LIB」/>' 因此，我認爲蝕不使用.war，或者至少不只是，並且使用這個.classpath文件。任何想法如何使maven正確生成此文件？ – jeff

我跟着： http://www.mkyong.com/maven/eclipse-web-deployment-assembly-maven-dependencies-issue/ 'MVN clean'然後'MVN蝕：日食-Dwtpversion = 2.0'然後'mvn install'然後「作爲...運行」 '/ project/org.eclipse.wst.common.component'已創建並且包含： ' ' 現在，無論我有在部署時的錯誤，無論是本地主機/項目/ servlet的導致了Err404 ... 第二個方法沒有任何改善的事情。 – jeff

使用M2E-WTP與WTP無縫集成：https://www.eclipse.org/m2e-wtp/

來源

2013-05-31 15:16:39

我添加了插件，但我沒有注意到任何改變。但是，我找到了一個解決方案：使用'maven-archetype-webapp'原型創建一個maven項目，而不是創建一個eclipse動態web項目並使用'configure> Convert to maven project'。的ressource不是found'：一些變化後，無論是在同'NoClassDefFoundError'無論是在'錯誤404再次失敗。在Eclipse服務器視圖中使用全新的服務器聲明（使用相同的tomcat安裝）修復了此問題。「Servers」項目配置文件上的差異沒有顯示任何相關的差異。還是謝謝！ :) – jeff

BTW，給您的個人資料，你可能在知道我的開發環境利益（安裝M2E-WTP後）： '名稱/ Version' 'Eclipse IDE中對Java EE開發\t 1.5.2.20130211-1820' 'M2E - Maven的集成爲Eclipse \t 1.3.1.20130219-1424' 'M2E - SLF4J的logback上記錄（可選）\t 1.3.1.20130219-1424' 'M2E-WTP - Maven的集成WTP（孵化）\t 0.17.0.20130212- 1821' 'Subversive SVN Connectors \t 3.0.0.I20130122-1700' 'Subversive SVN Team Provider \t 1.0.0.I20130122-1700' 'SVNK它1.3.8執行（可選）\t 3.0.0.I20121228-1700' '終端\t 1.1.2.201208131620' – jeff

安裝M2E-WTP應該工作後做的Maven>更新項目。 –

也許，您需要設置Maven的依賴關係展開組件的一部分。

Eclipse - > Project-> properties-> Deployment Assembly - > Add - > Java Build path entries->選擇maven dependencies。

這會讓你的pom依賴性獲得bundle作爲你的web檔案（web-inf/lib）的一部分。

來源

2013-06-02 09:32:55 Shinchan

權，但正如我在我的問題說（可能是太長：P），該設置被reseted每次你運行一個Maven構建或'的Maven>更新project' .. – jeff

Tomcat無法在Eclipse中的Tomcat上部署我的servlet（NoClassDefFoundError）

回答

相關問題