问题描述
我在一个项目中遇到了两次相同的 .jar(对我来说是 el-api.jar v2.1)的问题，因此，当我尝试使用 Tomcat 6 运行我的项目时出现以下错误堆栈.
I encountered the problem of having the same .jar (for my case, el-api.jar v2.1)twice for one project, hence, the following error stack when I try to run my project using Tomcat 6.
WARNING: Unexpected error forwarding to login page
javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/jasper/servlet/JasperLoader) of the current class, org/apache/jsp/login_jsp, 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 javax/el/ExpressionFactory used in the signature
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/jasper/servlet/JasperLoader) of the current class, org/apache/jsp/login_jsp, 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 javax/el/ExpressionFactory used in the signature
我找到了http://blog.springsource.com/2008/10/20/understanding-the-osgi-uses-directive/
但这没有用，因为解决方案影响了我项目的太多部分.
but that is not useful as the solution effects too many parts of my project.
我无法对 Tomcat 进行任何更改，并且该项目将被许多其他用户使用.
I can't make any changes to the Tomcat as well as the project will be used by many other user.
当前的解决方法是每次我们进行构建并使用 Tomcat6 时手动删除 el-api.jar.然后我们需要把 .jar 放回去，因为这是其他东西的要求.
The current work around is to manuelly delete the el-api.jar every time we do a build AND uses Tomcat6. Then we need to put the .jar back as that is requested for other stuff.
我使用 Maven 2 和 Maven 3 构建.(顺便说一句，有人知道在 Jruby 上使用 Maven3 吗?)
I am used Maven 2 and Maven 3 to build. (btw, did anyone know about use Maven3 on Jruby?)
谁能帮我解决这个问题?
Can anyone help me with the issue?
推荐答案
如果是，则将 el-api.jar 工件标记为 provided.
Then mark the el-api.jar artifact as provided, if it is.
当前的解决方法是每次我们进行构建并使用 Tomcat6 时手动删除 el-api.jar.然后我们需要把 .jar 放回去，因为这是其他东西的要求.
处理此问题的更好方法是在配置文件中声明依赖项并将其标记为 provided(例如在tomcat6"配置文件中)或不根据需要.
A much better way to handle this would be to declare the dependency inside profiles and to mark it as provided (e.g. in a "tomcat6" profile) or not depending on the needs.
这篇关于加载程序约束违规的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！