I recently updated to jBPM 3.1 and found that the TaskMgmtSession class doesn't check if a custom TaskInstance class has been declared when loading TaskInstances from Hibernate (e.g. TaskMgmtSession.getTaskInstance). I know that the actual class name is not configured in jbpm.cfg.xml (it used to be an option in jbpm 3.0). Is this a design issue, a bug, or something else? If it's a bug, perhaps the TaskInstanceFactory interface could be changed to add a static method that returns the class or class name of the Object constructed in the createTaskInstance method. The other option is to call the createTaskInstance and use the .class property.
bump, should I enter this into JIRA?