[ 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. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2194?page=com.atlassian.jira.plug... ] David Schlotfeldt commented on JBPM-2194: ----------------------------------------- I am not sure what you mean by "evaluator: from the ExpressionEvaluator javadoc: "the parseExpression() and evaluate() methods must be thread-safe. [...] global caching should therefore be static". " Seam calls the following two configuration settings and both use static variables: JbpmExpressionEvaluator.setExpressionEvaluator( new SeamExpressionEvaluator() ); UserCodeInterceptorConfig.setUserCodeInterceptor( new SeamUserCodeInterceptor() ); The problem is two separate applications cannot share the same class definitions since the two classes above use static variables. Threads have nothing to do with this. It doesn't matter if ExpressionEvaluator is thread safe or not. If I have project A that uses Seam and project B that doesn't use Seam but does use JBPM, then project Bwill still end up using SeamExpressionEvaluator since that setting is set on a static property -- so its shared between the two projects. It seems these two methods shouldn't be used at all PERIOD. They are not safe in an application server. In my opinion they should be deprecated since they are just asking for trouble. Is there an alternative approach I should tell Seam to switch to or does an alternative "application server safe" solution not exist at this time? Thanks David -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2194?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2194: ----------------------------------- Fix Version/s: jBPM 3.2.7 (was: jBPM 3.3.2) -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2194?page=com.atlassian.jira.plug... ] Alejandro Guizar resolved JBPM-2194. ------------------------------------ Resolution: Done -- 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