Link: Added: This issue depends JBESB-2818

See linked issue for details of jBPM method changes.

these are the changes that me and julien identified:

1) re-add Services.isCausedByStaleState(JbpmPersistenceException persistenceException) 
that method was refactored to DbPersistenceService.isLockingException(Exception exception).  so in the new implementation i'll call the migrated method.

2) re-add method JobSession.loadJobs

3) re-add class ExecuteJobsCommand.  implementation will be updated to delegate to ExecuteJobCommand (which was refactored) so that all those changes in ExecuteJobCommand (singular) will be leveraged by the new, re-added ExecuteJobsCommand

We have already updated the ESB codebase to reflect the changes, we are not intending to roll those back at this time.

This is really about the effect on customers, should they be using these methods/classes.

committed these changes as revision 5640 on branch jbpm-3.2-soa

This work just matches the work done within the platform build process.