Posted on 2009-04-08 09:40
ZhouFeng 閱讀(685)
評論(0) 編輯 收藏 所屬分類:
轉載 、
Web開發 、
Web服務器
在將一個Tomcat項目遷移到JBOSS時,出現了一點問題,就是配置好的eWebEditor不能用了,控制臺里報以下的錯誤
Exception in JSP: /eWebEditor.jsp:54
經過一番折騰后又發現了如下的出錯提示
java.lang.NoClassDefFoundError: org/dom4j/xpath/DefaultXPath
后來發現是dom4j.jar版本不對造成的問題,JBOSS自帶的版本會出現上述的情況
解決方法如下:
將eWebEditor里自帶的dom4j.jar(476K)的文件覆蓋掉jboss4\lib\dom4j.jar(297K)即可,本文參考以下的材料
The error "java.lang.NoClassDefFoundError: org/dom4j/xpath/DefaultXPath" underlines important changes to the dom4j XML library. It usually happens when you try to call this library's methods in runtime. Older versions that shipped with JBoss used to include Jaxen, but for whatever reason, it is no longer included. Users must download dom4j.jar (now at version 1.6.1) and then jaxen-full.jar (FCS-1.0). Now how to resolve this problem is tricky:
1. Put dom4j-1.3.jar in {jboss}/lib. This version is known good.
2. Put dom4j-1.6.1.jar and jaxen-full.jar in {jboss}/server/default/lib. Remove the old dom4j JARs that may exist in that directory.
The reason the newer version cannot be used with JBoss is unknown, but it does not work. The older version is used when reading JBoss-specific config files. The newer version of dom4j kicks in when the default server is initialized. This allows development of applications using newer versions of the XML API.
http://prideafrica.blogspot.com/2006/05/javalangnoclassdeffounderror.html