Java_Activiti5 _ cainiao also learns Activiti5 workflow _'s first knowledge of the simple structure of BPMN2.0 (5), activiti5bpmn2.0

Java_Activiti5 _ cainiao also learns Activiti5 workflow _'s first knowledge of the simple structure of BPMN2.0 (5), activiti5bpmn2.0

1 <? Xml version = "1.0" encoding = "UTF-8"?> <Definitions xmlns = "http://www.omg.org/spec/BPMN/20100524/MODEL" 3 xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: xsd = "http://www.w3.org/2001/XMLSchema" 4 xmlns: activiti = "http://activiti.org/bpmn" xmlns: bpmndi = "http://www.omg.org/spec/BPMN/20100524/DI" 5 xmlns: omgdc = "http://www.omg.org/spec/DD/20100524/DC" xmlns: omgdi = "http://www.omg.org/spec/DD/20100524/DI" 6 typeLanguage = "http: // w Ww.w3.org/2001/XMLSchema "expressionLanguage =" http://www.w3.org/1999/XPath "7 targetNamespace =" http://www.activiti.org/test "> 8 9 <! -- 10 BPMN 2.0 the root node is the definitions node. You can define multiple Process Definitions 11 in this element (however, we recommend that each file contain only one process definition to simplify maintenance during the development process ). 12 an empty process definition looks like the following. 13 note that the definitions element should contain at least the declaration of xmlns and targetNamespace. 14 targetNamespace can be any value, which is used to classify process instances. 15 --> 16 17 <! -- 18 the process element has two attributes: 19 id: This attribute is required and corresponds to the key attribute of the Activiti ProcessDefinition object. The 20' id can be used to start the process instance defined by the process, through the startProcessInstanceByKey method of RuntimeService. 21 In practice, this method is generally used to start the process. 22 name: This attribute is optional and corresponds to the name attribute of ProcessDefinition. The engine does not use this attribute by itself. 23 it can be used to display easy-to-view names in the flowchart. 24 --> 25 26 <process id = "myProcess" name = "My process" isExecutable = "true"> 27 28 <! -- StartEvent Start event, which is the entrance to our process --> 29 <startEvent id = "startevent1" name = "Start"> </startEvent> 30 31 <! -- A user task event is a task Declaration related to the operator in the process. --> 32 <userTask id = "usertask1" name = "User Task"> </userTask> 33 34 <! -- EndEvent: when the process reaches the end event, the entire process ends --> 35 <endEvent id = "endevent1" name = "End"> </endEvent> 36 37 <! -- SequenceFlow is used to connect the elements. These connections have the source and target attributes and define the direction of the connection. --> 38 <sequenceFlow id = "flow1" sourceRef = "startevent1" targetRef = "usertask1"> </sequenceFlow> 39 <sequenceFlow id = "flow2" sourceRef = "usertask1" targetRef = "endevent1"> </sequenceFlow> 40 </process> 41 <bpmndi: bpmndi1_id = "BPMNDiagram_myProcess"> 42 43 <! -- 44 The following defines the coordinates of some process events 45 --> 46 47 <bpmndi: BPMNPlane bpmnElement = "myProcess" id = "BPMNPlane_myProcess"> 48 <bpmndi: BPMNShape bpmnElement = "startevent1" 49 id = "BPMNShape_startevent1"> 50 <omgdc: bounds height = "35.0" width = "35.0" x = "60.0" y = "130.0"> </omgdc: Bounds> 51 </bpmndi: BPMNShape> 52 <bpmndi: BPMNShape bpmnElement = "usertask1" id = "BPMNShape_usertask1"> 53 <omgdc: bounds height = "55.0" width = "105.0" x = "190.0" y = "119.0"> </omgdc: Bounds> 54 </bpmndi: BPMNShape> 55 <bpmndi: BPMNShape bpmnElement = "endevent1" id = "BPMNShape_endevent1"> 56 <omgdc: bounds height = "35.0" width = "35.0" x = "390.0" y = "130.0"> </omgdc: Bounds> 57 </bpmndi: BPMNShape> 58 <bpmndi: BPMNEdge bpmnElement = "flow1" id = "BPMNEdge_flow1"> 59 <omgdi: waypoint x = "95.0" y = "147.0"> </omgdi: waypoint> 60 <omgdi: waypoint x = "190.0" y = "146.0"> </omgdi: waypoint> 61 </bpmndi: BPMNEdge> 62 <bpmndi: BPMNEdge bpmnElement = "flow2" id = "BPMNEdge_flow2"> 63 <omgdi: waypoint x = "295.0" y = "146.0"> </omgdi: waypoint> 64 <omgdi: waypoint x = "390.0" y = "147.0"> </omgdi: waypoint> 65 </bpmndi: BPMNEdge> 66 </bpmndi: BPMNPlane> 67 </bpmndi: BPMNDiagram> 68 </definitions>