So I presume this is a bug... at least in that the latest version of jBPM is dependent on obsolete versions of Hibernate.
But is it a bug in jBPM 5.2, or Hibernate 3.5+?
Is there an updated Taskorm.xml that will work correctly with Hibernate 3.5+?
If I replace all the createdBy and actualOwner instances in Taskorm.xml as specified above, is that sufficient to use Hibernate 3.5.Final?
Thank you.