加载器约束冲突：解析接口方法“javax.servlet.jsp.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V”时
我在 Tomcat 7 中部署 WAR 时遇到此错误。我使用 JDeveloper 11 进行开发。
“java.lang.LinkageError：加载器约束冲突：解析接口方法“javax.servlet.jsp.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V”时，类加载器（org/apache/catalina/的实例）当前类的 com/sun/faces/config/ConfigureListener 和类加载器（实例org/apache/catalina/loader/StandardClassLoader) 对于解析类 javax/servlet/jsp/JspApplicationContext，对于签名中使用的类型 p.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V 有不同的 Class 对象”
我有用谷歌搜索答案并找到了答案，但似乎没有什么可以解决我的问题。我知道这与我的 /WEB-INF/lib 中的 JAR 有关，但我不知道是什么导致了错误。
这些是我在 /WEB-INF/lib 中的 JAR：
adf-controller-api.jaradf-controller-rt-common.jar>adf-controller-security.jaradf-controller.jaradf-dt-at-rt.jaradf-richclient-api-11.jaradf-richclient-impl-11.jaradf-share-base.jaradf -share-ca.jaradf-share-security.jaradf-share-support.jaradf-transactions-dt.jar代码>adfdt_common.jaradflibfilter.jaradflogginghandler.jaradfm.jaradfmweb.jaradfsharembean.jarcache.jarcommons-el.jardb-ca.jardvt-databindings.jardvt-faces.jardvt-facesbindings.jardvt-jclient.jardvt-trinidad.jardvt-utils.jarglassfish.el_2.2.0.jarglassfish.jsf_1.2.9.0.jarglassfish.jstl_1.2.0.1.jargroovy-all-1.6.3.jaridentitystore.jarinspect4.jarjavatools-nodeps.jarjavax.activation_1.1.0.0_1-1.jarjavax.ejb_3.0.1.jarjavax.jsf_1.0.0.0_1-2.jarjavax.jsp_1.1.0.0_2-1.jarjavax.servlet_1.0.0.0_2-5.jarjdev-cm.jarjewt4.jarjsp-el-api.jarojdbc14.jarojmisc.jaroracle- el.jaroracle-page-templates.jarshare.jartrinidad-api.jartrinidad-impl.jarwls.jsf.di.jarxmlparserv2.jar
如何解决？
I got this error while deploying the WAR in Tomcat 7. I have carried out the development using JDeveloper 11.
"java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type p.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V used in the signature"
I have googled for the answers and have found answers, but nothing seems to work for my problem. I understand that it is something to do with the JARs that I have in my /WEB-INF/lib, but I don't know which causes the error.
These are the JARs I have in /WEB-INF/lib:
adf-controller-api.jaradf-controller-rt-common.jaradf-controller-security.jaradf-controller.jaradf-dt-at-rt.jaradf-richclient-api-11.jaradf-richclient-impl-11.jaradf-share-base.jaradf-share-ca.jaradf-share-security.jaradf-share-support.jaradf-transactions-dt.jaradfdt_common.jaradflibfilter.jaradflogginghandler.jaradfm.jaradfmweb.jaradfsharembean.jarcache.jarcommons-el.jardb-ca.jardvt-databindings.jardvt-faces.jardvt-facesbindings.jardvt-jclient.jardvt-trinidad.jardvt-utils.jarglassfish.el_2.2.0.jarglassfish.jsf_1.2.9.0.jarglassfish.jstl_1.2.0.1.jargroovy-all-1.6.3.jaridentitystore.jarinspect4.jarjavatools-nodeps.jarjavax.activation_1.1.0.0_1-1.jarjavax.ejb_3.0.1.jarjavax.jsf_1.0.0.0_1-2.jarjavax.jsp_1.1.0.0_2-1.jarjavax.servlet_1.0.0.0_2-5.jarjdev-cm.jarjewt4.jarjsp-el-api.jarojdbc14.jarojmisc.jaroracle-el.jaroracle-page-templates.jarshare.jartrinidad-api.jartrinidad-impl.jarwls.jsf.di.jarxmlparserv2.jar
How can I solve it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您的
/WEB-INF/lib中不应该有 servletcontainer 特定的库。至少以下内容应该是由 Tomcat 本身提供的：glassfish.el_2.2.0.jarjavax.jsp_1.1.0.0_2-1.jarjavax.servlet_1.0.0.0_2-5.jarjsp-el-api.jar删除它们。该异常是由
javax.jsp_1.1.0.0_2-1.jar引起的，该异常与 Tomcat 自己的异常不同。另请参阅：
You should not have servletcontainer-specific libraries in your
/WEB-INF/lib. At least the following ones are supposed to be already provided by Tomcat itself:glassfish.el_2.2.0.jarjavax.jsp_1.1.0.0_2-1.jarjavax.servlet_1.0.0.0_2-5.jarjsp-el-api.jarRemove them. The particular exception is caused by the
javax.jsp_1.1.0.0_2-1.jarone, which is different from Tomcat's own one.See also:
将项目从 WAS6 迁移到 WAS 7 时，我遇到了同样的错误。修复方法如下：
更新 web.xml：
一个。打开项目名称\src\main\webapp\WEB-INF\web.xml
b.添加以下监听器：
com.sun.faces.config.ConfigureListener
更新web.xml
c.构建项目并将其部署到 Websphere
更改加载程序顺序：
一个。打开Websphere应用程序服务器控制台
b.转到：应用>>应用程序类型>> WebSphere 企业应用程序
c.点击项目
d.点击“类加载和更新检测”
e.选择“首先使用父加载器加载的类”
f.单击“应用”
禁用 JSP 类重新加载
一个。转到：应用>>应用程序类型>> WebSphere 企业应用程序
b.点击项目
c.单击 JSP 和 JSF 选项
d.取消选中“JSP 启用类重新加载”
e.单击“确定”
更改 JSF 实现
一个。转到：应用>>应用程序类型>> WebSphere 企业应用程序
b.点击项目
c.单击 JSP 和 JSF 选项
d.在 JSF 实现下选择“MyFaces 1.2”
启动项目
I had the same error when migrating a project from WAS6 to WAS 7. Here is the fix:
Update web.xml:
a. Open Project_name\src\main\webapp\WEB-INF\web.xml
b. Add the following listener:
Com.sun.faces.config.ConfigureListener
c. Build the project and deploy it to Websphere
Change loader order:
a. Open Websphere application server Console
b. Go to: Applications >> Application Types >> WebSphere enterprise applications
c. Click at the project
d. Click “Class loading and update detection”
e. Choose “Classes loaded with parent loader first”
f. Click Apply
Disable JSP class reloading
a. Go to: Applications >> Application Types >> WebSphere enterprise applications
b. Click at the project
c. Click at JSP and JSF options
d. Uncheck “JSP enable class reloading”
e. Click OK
Change JSF Implementation
a. Go to: Applications >> Application Types >> WebSphere enterprise applications
b. Click at the project
c. Click at JSP and JSF options
d. Choose “MyFaces 1.2” under JSF Implementation
Start the Project