I know that the process definition in Activiti are versioned. So, If you deploy a new version, new process instances will run in the newest process definition, old process instances keep running against the original version.
What about the Java classes (for example Java service tasks or event listener implementations) that are present in the activiti-engine’s classpath. Can these be versioned?
Question 1:
Can I force the Activiti engine to use version1 of the Java jar against version1 of the process definition and version2 of the jar against version 2 of the process definition.
Question 2:
Basically, I need to add few more lines of code to the existing 'service task' as part of version2 change but I don't want these lines to be executed for the old in-flight instances. How can I achieve this?
Thanks