Activiti the spring integration activiti-modeler5.16 instance of the custom process (iv): deployment process Definition

Note: (1) Environment construction: Activiti Custom process Spring Integration activiti-modeler5.16 Example (i): Environment construction
(2) Create process Model: Activiti custom process Spring Integration activiti-modeler5.16 Instance (ii): Create process Model
(3) Process Model list show: Activiti custom process Spring Integration activiti-modeler5.16 Instance (iii): Process Model list Show


1.maven Guide Package and some of the basic spring configuration and no changes in the previous, it is still the same as well.


2. There are 3 tables related to the process definition, namely Act_ge_bytearray, Act_re_procdef and Act_re_deployment. Of course, if it is more accurate, in my custom process, the process definition needs to use the data related to the process model, or it can be said that the process definition is related to four tables, including the model table.


3. Background business code, according to the front-end incoming Deploymentid deployment process definition, here or use Repositoryservice to operate, the general process is based on Deploymentid query out the creation of the model when the relevant files, Then perform a certain conversion after the deployment:

[Java]View PlainCopy  

2. /**
4. * Deployment process definition based on model ID
6. *
8. * @author: Tuzongxun
10. * @Title: Deploye
12. * @param @param Activitimodel
14. * @param @param redirectattributes
16. * @param @return
18. * @return Object
20. * @date Mar, 12:30:05 PM
22. * @throws
24. */
26. @RequestMapping (value = "/deploye.do", method = Requestmethod.post, produces = "Application/json;charset=utf-8 ")  
28. @ResponseBody
30. Public Object Deploye (@RequestBody activitimodel Activitimodel,
32. HttpServletRequest req) {
34. map<string, object> map = new hashmap<string, object> ();
36. Boolean islogin = this.islogin (req);
38. if (islogin) {
40. String modelid = Activitimodel.getid ();
42. try {
44. Model modeldata = Repositoryservice.getmodel (modelid);
46. Objectnode Modelnode = (objectnode) new Objectmapper ()
48. . Readtree (Repositoryservice
50. . Getmodeleditorsource (Modeldata.getid ()));
52. byte[] bpmnbytes = null;
54. Bpmnmodel model = new Bpmnjsonconverter ()
56. . Converttobpmnmodel (Modelnode);
58. Bpmnbytes = new Bpmnxmlconverter (). Converttoxml (model);
60. String processName = modeldata.getname () + ". Bpmn20.xml";
62. Deployment Deployment = Repositoryservice.createdeployment ()
64. . Name (Modeldata.getname ())
66. . addstring (ProcessName, new String (bpmnbytes)). deploy ();
68. if (Deployment! = null && deployment.getid () = null) {
70. Map.put ("IsLogin", "yes");
72. Map.put ("UserName",
74. (String) Req.getsession (). getattribute ("UserName"));
76. Map.put ("result", " success");
78. }
80. } catch (Exception e) {
82. E.printstacktrace ();
88. }
90. } Else {
92. Map.put ("IsLogin", "no");
94. }
96. return map;
98. }

4.angular JS foreground code, here actually just called a method in the previous Model list page, so the front-end code is still the code in the previous article, but the method is called here:

[JavaScript]View PlainCopy 

2. Angular.module (' Activitiapp ')
4. . Controller (' modelctr ', [' $rootScope ',' $scope ',' $http ',' $location ', function ($rootScope, $scope, $http, $location) {
6. $scope. init=function () {
8. $http. Post ("./modellist.do"). Success (function (result) {
10. if (result.islogin==="yes") {
12. $rootScope. Username=result.username;
14. Console.log (Result.data);
16. $scope. Modellist=result.data;
18. }else{
20. $location. Path ("/login");
22. }
24. });
26. }
28. //deployment process definition, here is the main way
30. $scope. deploye=Function (model) {
32. Console.log (model);
34. $http. Post ("./deploye.do", model). Success (function (deployresult) {
36. $location. Path ("/processlist");
38. });
40. }
44. $scope. update=Function (modelid) {
46. window.open ("http://localhost:8080/activitiTest2/service/editor?id=" +modelid);
48. }
50. }])

5. Before deployment, we can see that when a model is originally created, only one and two data will appear in the database in model table and ByteArray two tables respectively. When successfully deployed, the ByteArray table will add two more data, and the two tables of Act_re_procdef and Act_re_deployment will each appear with a corresponding data. ByteArray table at this time data such as:

The data in the Act_re_procdef table is as follows:

The data in Act_re_deployment is as follows:

It should be noted that these data in the subsequent operation of the need to use, if there is a lack of, will inevitably affect the subsequent operation.

Activiti activiti-modeler5.16 instance of the spring consolidation of the custom process (iv): deployment process definition