unlock in new transaction

Author: qqmyers

src/main/java/edu/harvard/iq/dataverse/workflow/WorkflowServiceBean.java

@@ -78,6 +78,9 @@ public class WorkflowServiceBean {
     @EJB
     EjbDataverseEngine engine;
 
+    @EJB
+    WorkflowServiceBean self;  
+    
     @Inject
     DataverseRequestServiceBean dvRequestService;
 
@@ -269,7 +272,7 @@ private void rollback(Workflow wf, WorkflowContext ctxt, Failure failure, int la
 
         logger.log( Level.INFO, "Removing workflow lock");
         try {
-            unlockDataset(ctxt);
+            self.unlockDataset(ctxt);
         } catch (CommandException ex) {
             logger.log(Level.SEVERE, "Error restoring dataset locks state after rollback: " + ex.getMessage(), ex);
         }
@@ -354,7 +357,7 @@ void lockDataset(WorkflowContext ctxt, DatasetLock datasetLock) throws CommandEx
     }
 
     @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
-    void unlockDataset(WorkflowContext ctxt) throws CommandException {
+    public void unlockDataset(WorkflowContext ctxt) throws CommandException {
         /*
          * Since the lockDataset command above directly persists a lock to the database,
          * the ctxt.getDataset() is not updated and its list of locks can't be used.
@@ -407,7 +410,7 @@ private void workflowCompleted(Workflow wf, WorkflowContext ctxt) {
                 lockDataset(ctxt, lock);
                 ctxt.getDataset().addLock(lock);
 
-                unlockDataset(ctxt);
+                self.unlockDataset(ctxt);
                 ctxt.setLockId(null); //the workflow lock
                 //Refreshing merges the dataset
                 ctxt = refresh(ctxt);