Activiti 5.3：流程活动自动与手工触发执行

Activiti 5.3支持流程活动自动执行与手工触发执行。其中，自动执行是指，在启动流程之前，准备流程所需要的控制流程进度的变量数据，启动流程之后，无需外部干预，就能够按照预定义的流程执行；手工触发执行是指，执行到流程中某个个结点后流程暂时停止运行，直到收到外部发送的信号以后，才会继续向前推进，这样情况可以更加精细地控制流程。

下面主要通过基于Activiti 5.3的<parallelGateway>、<serviceTask>、<receiveTask>、<userTask>元素来看一下。首先，我们在测试的过程中，用到JUnit 3.x，为了方便，这里给了一层封装，代码如下所示：

package org.shirdrn.workflow.activiti; import junit.framework.TestCase; import org.activiti.engine.FormService; import org.activiti.engine.HistoryService; import org.activiti.engine.IdentityService; import org.activiti.engine.ManagementService; import org.activiti.engine.ProcessEngine; import org.activiti.engine.ProcessEngines; import org.activiti.engine.RepositoryService; import org.activiti.engine.RuntimeService; import org.activiti.engine.TaskService; /** * @author shirdrn */ public abstract class AbstractTest extends TestCase { private ProcessEngine processEngine; protected String deploymentId; protected RepositoryService repositoryService; protected RuntimeService runtimeService; protected TaskService taskService; protected FormService formService; protected HistoryService historyService; protected IdentityService identityService; protected ManagementService managementService; @Override protected void setUp() throws Exception { super.setUp(); if(processEngine==null) { processEngine = ProcessEngines.getDefaultProcessEngine(); } repositoryService = processEngine.getRepositoryService(); runtimeService = processEngine.getRuntimeService(); taskService = processEngine.getTaskService(); formService = processEngine.getFormService(); historyService = processEngine.getHistoryService(); identityService = processEngine.getIdentityService(); managementService = processEngine.getManagementService(); initialize(); } @Override protected void tearDown() throws Exception { super.tearDown(); destroy(); } protected abstract void initialize() throws Exception; protected abstract void destroy() throws Exception; }

这里面，主要是在测试之前做一些初始化工作，主要包括流程引擎实例的构建，及其流程提供的基本服务。下面测试会用到该抽象类。

自动执行

<serviceTask>元素，可以实现自动活动，语法如下所示：

<serviceTask id="serviceTaskId" name="serviceTaskName" activiti:class="org.shirdrn.workflow.activiti.gateway.ServiceTaskClass"/>

其中，activiti:class属性为该结点对应的处理类，该类要求实现org.activiti.engine.delegate.JavaDelegate接口，该接口定义如下所示：

package org.activiti.engine.delegate; public interface JavaDelegate { void execute(DelegateExecution execution) throws Exception; }

execute方法的参数DelegateExecution execution可以在流程中各个结点之间传递流程变量。

下面给出一个具体的例子：

自动执行的流程，如图所示：

 

对应的流程定义文件为GatewayTest.testAutomaticForkJoin.bpmn20.xml，如下所示：

<?xml version="1.0" encoding="UTF-8"?> <definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:activiti="http://activiti.org/bpmn" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:omgdc="http://www.omg.org/spec/DD/20100524/DC" xmlns:omgdi="http://www.omg.org/spec/DD/20100524/DI" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.activiti.org/test"> <process id="AutomaticParalellBasedForkJoin" name="AutomaticParalellBasedForkJoin"> <startEvent id="startevent7" name="Start"></startEvent> <parallelGateway id="parallelgateway12" name="Fork"></parallelGateway> <serviceTask id="servicetask3" name="Task 1" activiti:class="org.shirdrn.workflow.activiti.gateway.ServiceTask1"></serviceTask> <serviceTask id="servicetask4" name="Task 2" activiti:class="org.shirdrn.workflow.activiti.gateway.ServiceTask2"></serviceTask> <serviceTask id="servicetask5" name="Task 3" activiti:class="org.shirdrn.workflow.activiti.gateway.ServiceTask3"></serviceTask> <parallelGateway id="parallelgateway13" name="First Join"></parallelGateway> <serviceTask id="servicetask6" name="Task 4" activiti:class="org.shirdrn.workflow.activiti.gateway.ServiceTask4"></serviceTask> <parallelGateway id="parallelgateway14"></parallelGateway> <endEvent id="endevent7" name="End"></endEvent> <sequenceFlow id="flow45" name="" sourceRef="startevent7" targetRef="parallelgateway12"></sequenceFlow> <sequenceFlow id="flow46" name="" sourceRef="parallelgateway12" targetRef="servicetask3"></sequenceFlow> <sequenceF