PUBLIC - Liferay Portal Community Edition

• Type: Bug
• Status: Analyzed
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 6.0.6 GA, 6.1.0 CE RC1, 6.0.X EE
• Fix Version/s: Issues Backlog
• Component/s: Kaleo, Workflow Portlets
• Labels:

  • kaleo
  • workflow,
• Environment:

  Tomcat 6.0.32 + MySQL 5.1.58. 6.0.x Revision 87920.
  Tomcat 6.0.32 + MySQL 5.1.58. 6.1.x Revision 87920.

When changing the workflow context of a workflow instance by calling WorkflowInstanceManagerUtil.updateWorkflowContext() (forwarding to Kaleo implementation of WorkflowInstanceManager), the workflow context is changed in the workflow instance returned by the method, but the change is not committed to the database.

KaleoInstanceLocalServiceImpl.updateKaleoInstance() should call KaleoInstancePersistence.update() after changing the workflow context.

Untested correction is the following (note kaleoInstancePersistence.update()):

public KaleoInstance updateKaleoInstance(
		long kaleoInstanceId, Map<String, Serializable> workflowContext,
		ServiceContext serviceContext)
	throws PortalException, SystemException {

	KaleoInstance kaleoInstance = kaleoInstancePersistence.findByPrimaryKey(
		kaleoInstanceId);

	kaleoInstance.setWorkflowContext(
		WorkflowContextUtil.convert(workflowContext));

	kaleoInstancePersistence.update(kaleoInstance, false);

	return kaleoInstance;
}

The JBPM implementation correctly calls jbpmContext.save(token) in WorkflowInstanceManagerImpl.updateWorkflowContext().

1. 

   LPS-20059.patch

   15/Aug/11 11:18 AM

   0.7 kB

   Soeren Unruh

• Assignee:

  SE Support

  Reporter:

  Soeren Unruh

• Created:

  15/Aug/11 9:28 AM

  Updated:

  29/Aug/11 10:43 AM