[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2194) cant share jars
[
https://jira.jboss.org/jira/browse/JBPM-2194?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-2194:
----------------------------------------
In relation to JbpmExpressionEvaluator and its static fields:
* evaluator: from the ExpressionEvaluator javadoc: "the parseExpression() and
evaluate() methods must be thread-safe. [...] global caching should therefore be
static".
* variableResolver and functionMapper: these fields may be left unset, in which case the
objects will be read from the jbpm.variable.resolver and jbpm.function.mapper fields in
the jbpm configuration. If Seam sets the objects statically instead of using the
configuration file, that is a problem on the Seam side.
Regarding UserCodeInterceptor, it should be settable in the configuration file as well,
and Seam modified to make use of the configuration file.
cant share jars
---------------
Key: JBPM-2194
URL: https://jira.jboss.org/jira/browse/JBPM-2194
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.6.SP1
Reporter: David Schlotfeldt
Priority: Critical
You can't share the jbpm jars. Each application must have its own copy since classes
like
http://anonsvn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.6.SP1/modules/cor...
use static variables. This is a LARGE issue.
JBoss Seam for example set settings on UserCodeInterceptorConfig and
JbpmExpressionEvaluator. These settings will mess will affect ALL applications that share
the same class definitions since the settings are a on static variable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira