[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2800) java.lang.NoSuchMethodError: javax.el.ExpressionFactory.newInstance()
[
https://jira.jboss.org/browse/JBPM-2800?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu commented on JBPM-2800:
-----------------------------------
Whenever I put juel-2.2.1.jar to the webapp's lib directory on tomcat-6.0.2x and try
to open a JSP. Then I got this error.
java.lang.LinkageError: loader constraints violated when linking
javax/el/ExpressionFactory class
Seems this is the problem of tomcat's classloader, it didnot allow we use different
version of javax.el in its webapp.
One of solution is using juel.jar to replace el-api.jar from the tomcat lib directory.
Another solution is using OSGi to seperate juel.jar from tomcat's classloader.
I must say that both of these solutions are not easy.
I think your patch is good and could solve this NoSuchMethodError. But whenever we used
juel.jar, the version conflict wil still here.
java.lang.NoSuchMethodError: javax.el.ExpressionFactory.newInstance()
----------------------------------------------------------------------
Key: JBPM-2800
URL: https://jira.jboss.org/browse/JBPM-2800
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Heiko Braun
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: JBPM-2800.patch
Caused by: java.lang.NoSuchMethodError:
javax.el.ExpressionFactory.newInstance(Ljava/util/Properties;)Ljavax/el/ExpressionFactory;
at
org.jbpm.pvm.internal.el.JbpmElFactoryImpl.createExpressionFactory(JbpmElFactoryImpl.java:111)
at org.jbpm.pvm.internal.el.Expression.initExpressionObjects(Expression.java:94)
at org.jbpm.pvm.internal.el.Expression.create(Expression.java:63)
at
org.jbpm.jpdl.internal.activity.SubProcessBinding.parseJpdl(SubProcessBinding.java:109)
at org.jbpm.jpdl.internal.activity.JpdlBinding.parse(JpdlBinding.java:52)
at org.jbpm.jpdl.internal.xml.JpdlParser.parseActivities(JpdlParser.java:320)
at org.jbpm.jpdl.internal.xml.JpdlParser.parseDocumentElement(JpdlParser.java:250)
at org.jbpm.pvm.internal.xml.Parser.parseDocument(Parser.java:476)
at org.jbpm.pvm.internal.xml.Parser.execute(Parser.java:396)
at org.jbpm.pvm.internal.xml.Parse.execute(Parse.java:158)
at org.jbpm.pvm.internal.repository.ProcessDeployer.deploy(ProcessDeployer.java:68)
at org.jbpm.pvm.internal.repository.DeployerManager.deploy(DeployerManager.java:46)
at
org.jbpm.pvm.internal.repository.RepositorySessionImpl.getObject(RepositorySessionImpl.java:129)
at
org.jbpm.pvm.internal.query.ProcessDefinitionQueryImpl.execute(ProcessDefinitionQueryImpl.java:72)
at org.jbpm.pvm.internal.query.AbstractQuery.execute(AbstractQuery.java:87)
at
org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira