while performing some performance measurements against our application I noticed that Activiti seems to utilize a kind of unexpected caching strategy: Retrieved objects seem to be cached only within a DbSqlSession (attached to a CommandContext) instead of a cache lifetime that spans a transaction (which I would have naively expected).
Even after fixing ACT-1040 this causes multiple retrievals of the same TaskEntity within the same transaction when invoking multiple TaskService methods for the same task (e.g., getIdentityLinksForTask, getVariablesLocal, etc.).
Is this intentional? Are there any recommendations how to extend the cache life-span to the complete transaction duration?
