CN103383645B - Code generating method and system - Google Patents

Abstract

The invention discloses a code generation method and system, the system comprising: a static form reading module, a Java server page (JSP) generation module, a data persistence layer generation module, a controller generation module and a configuration file generation module; The JSP generation module generates a view layer JSP file; the data persistence layer generation module generates a simple JAVA object (POJO) class file and a data access object (DAO) class file; the controller generation module generates a controller Java class file; The configuration file generation module generates an Extensible Markup Language (XML) configuration file. By adopting the technical scheme of the invention, business codes can be efficiently generated according to the specific frameworks of different software to be developed, and the development cost can be reduced.

Description

Code generation method and system

technical field

The invention relates to business code generation technology, in particular to a code generation method and system.

Background technique

At present, it has become a trend to use code generation tools to assist project development, solve the problem of developers' code irregularities, improve development efficiency and software code reuse rate, and reduce development costs. The business code generated by the specific framework can only generate code with auxiliary functions to realize the basic business logic of adding, deleting, modifying, and checking; at the same time, the current code generation tool controls business logic changes, but configuration or learning existing The implementation of the rule engine is more complicated and the cost is higher.

Therefore, how to efficiently generate business codes according to the specific frameworks of different software to be developed and reduce development costs has become an urgent problem to be solved.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a code generation method and system to efficiently generate business codes according to the specific frameworks of different projects to be developed and reduce development costs.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

The present invention provides a code generation system, which includes:

The static form reading module is used to read the code of the control of the static form, and determine the attribute of the control according to the code of the control of the static form; the control is encapsulated as a control object, and according to the corresponding attribute, storing the control object in a corresponding variable set;

The server page (JSP, JavaServerPages) generation module is used to generate JavaScript codes corresponding to different attribute variable sets according to the attributes of the control objects in the variable set, and generate a view according to the JavaScript codes and the codes of the controls of the static form layer JSP file;

The data persistence layer generating module is used to read the business data table corresponding to the form data operation, and according to the data structure of the business data table, generate simple JAVA objects (POJO, POJO, PlainOldJavaObjects) class files, and data access object (DAO, DataAccessObject) class files;

A controller generation module, configured to generate a controller Java class file corresponding to the name of the static form according to the attributes of the control object in the variable set, and the instance of the POJO class file and the instance of the DAO class file, Described controller Java class file comprises: the controller Java class file of processing viewing form request and the controller Java class file of processing submission form request;

The configuration file generating module is configured to generate an Extensible Markup Language (XMLExtensibleMarkupLanguage) configuration file, the attribute of the action node in the XML configuration file corresponds to the name of the static form.

Preferably, the JSP generation module is also used to generate an empty JSP file whose name corresponds to the name of the static form; add an external cascading style sheet (CSS, CascadingStyleSheet) file, a static hyperlink to the JSP file Text markup language (HTML, HypertextMarkupLanguage) tag; add the code of the control of the static form to the main body (body) tag in the JSP file;

Determine the variable of the control that reads form data in the static form, generate the tag front-end code corresponding to the variable of the control that reads form data, and the JavaScript code that assigns a value to the variable of the control that reads form data, And write described JSP file; Determine the variable of the non-empty control that saves form data and the data that requires preservation in the described static form, generates the JavaScript code of verification form control legitimacy, and writes described JSP file;

Generate JavaScript codes to prevent repeated form submissions, and write them into the JSP file.

Preferably, the data persistence layer generation module is also used to generate an empty POJO class file corresponding to the name of the business data table, obtain the field type and field name of the business data table, and send the POJO class file Write the attribute corresponding to the field type and field name of the business data table;

Generate an empty DAO class file corresponding to the name of the business data table, write the attribute corresponding to the field type and field name of the business data table to the DAO class file;

Instantiate the first string variable (StringBuilder), generate a source file that calls the basic operations of adding, deleting, modifying, and checking the Hibernate interface, write the source file into the first StringBuilder, and write the first StringBuilder Write the DAO class file.

Preferably, the controller generating module is further configured to generate an empty first controller Java class file for processing a request to view a form, and the name of the first controller Java class file corresponds to the name of the static form;

Instantiate the second StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the first controller Java class file, and generate the Java class file corresponding to the first controller An acquisition (getter) application and a setting (setter) application of the instance variable, adding the getter application and the setter application to the first StringBuilder;

Generate an execute application corresponding to the Java class file of the first controller class, and add the execute application to the first StringBuilder;

Adding the first StringBuilder to the first controller Java class file;

Generate an empty second controller Java class file for processing the submitted form request, the name of the second controller Java class file corresponds to the name of the static form;

Instantiate the third StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the second controller Java class file, and generate a getter application and a setter corresponding to the instance variable application, adding the getter application and the setter application to the third StringBuilder;

Generate an execute application corresponding to the Java class file of the second controller, and add the execute application to the third StringBuilder;

Add the third StringBuilder to the second controller Java class file.

Preferably, the configuration file generation module is also used to generate an empty XML configuration file, generate a corresponding package node and an action node corresponding to the static form name in the XML configuration file, and generate an empty XML configuration file;

Instantiate the fourth StringBuilder, and add the statement of the XML configuration file to the fourth StringBuilder;

Generate the package node of the XML configuration file and the action node corresponding to the name of the static form, and add them to the fourth StringBuilder;

Write the fourth StringBuilder into the empty XML configuration file.

The present invention also provides a code generation method, the method comprising:

Read the code of the control of the static form, determine the property of the control according to the code of the control of the static form; encapsulate the control into a control object, and store the control object according to the property corresponding to the control object to the corresponding variable set;

Generate JavaScript codes corresponding to different attribute variable sets according to the attributes of the control objects in the variable set, and generate a view layer JSP file according to the JavaScript codes and the codes of the controls of the static form;

Read the business data table, according to the data structure of the business data table, generate the simple JAVA object POJO class file and the data access object DAO class file corresponding to the name of the business data table respectively;

According to the attribute of the control object in the variable set, and the instance of the POJO class file and the instance of the DAO class file, generate a controller Java class file corresponding to the name of the static form, and the controller Java class file Including: the controller Java class file that handles the request to view the form and the controller Java class file that handles the request to submit the form;

An XML configuration file is generated, and the attribute of the action node in the XML configuration file corresponds to the name of the static form.

Preferably, according to the attributes of the control objects in the variable set, JavaScript codes corresponding to different attribute variable sets are generated, and according to the JavaScript code and the codes of the controls of the static form, a view layer JSP file is generated, including:

Generate an empty JSP file whose name is corresponding to the name of the static form; add an external CSS file and a static HTML tag in the JSP file; add the code of the control of the static form to the main body in the JSP file Inside the body tag;

Determine the variable of the control that reads form data in the static form, generate the tag front-end code corresponding to the variable of the control that reads form data, and the JavaScript code that assigns a value to the variable of the control that reads form data, And write described JSP file; Determine the variable of the non-empty control that saves form data and the data that requires preservation in the described static form, generates the JavaScript code of verification form control legitimacy, and writes described JSP file;

Generate JavaScript codes to prevent repeated form submissions, and write them into the JSP file.

Preferably, the reading of the business data table generates, according to the data structure of the business data table, POJO class files and data access object DAO class files respectively corresponding to the names of the business data tables, including:

Generate an empty POJO class file corresponding to the name of the business data table, obtain the field type and field name of the business data table, and write the field type and field name of the business data table to the POJO class file corresponding attributes;

Generate an empty DAO class file corresponding to the name of the business data table, write the attribute corresponding to the field type and field name of the business data table to the DAO class file;

Instantiate the first StringBuilder, generate the source file for the basic operations of adding, deleting, modifying, and checking the Hibernate interface, write the source file into the first StringBuilder, and write the first StringBuilder into the DAO class files.

Preferably, generating a controller Java class file corresponding to the name of the static form according to the attributes of the control object in the variable set, and the instance of the POJO class file and the instance of the DAO class file, including:

Generate an empty first controller Java class file for processing viewing form requests, the name of the first controller Java class file corresponds to the name of the static form;

Instantiate the second StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the first controller Java class file, and generate the Java class file corresponding to the first controller The getter application and the setter application of the instance variable, adding the getter application and the setter application to the first StringBuilder;

Generate an execute application corresponding to the first controller class Java class file, and add the execute application to the first StringBuilder;

Adding the first StringBuilder to the first controller Java class file;

Generate an empty second controller Java class file for processing the submitted form request, the name of the second controller Java class file corresponds to the name of the static form;

Instantiate the third StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the second controller Java class file, and generate a getter application and a setter corresponding to the instance variable application, adding the getter application and the setter application to the third StringBuilder;

Generate an execute application corresponding to the Java class file of the second controller, and add the execute application to the third StringBuilder;

Add the third StringBuilder to the second controller Java class file.

Preferably, the generating Extensible Markup Language XML configuration file, the attribute of the action node in the XML configuration file corresponds to the name of the static form, including:

Generate an empty XML configuration file, generate a corresponding package node and an action node corresponding to the static form name in the XML configuration file, and generate an empty XML configuration file;

Instantiate the fourth StringBuilder, and add the statement of the XML configuration file to the fourth StringBuilder;

Generate the package node of the XML configuration file and the action node corresponding to the name of the static form, and add them to the fourth StringBuilder;

Write the fourth StringBuilder into the empty XML configuration file.

The technical scheme of the code generation of the workflow web page (Web) application based on the model-view-controller (MVC, Model-View-Controller) architecture provided by the present invention generates the front-end code of the manual activity page through the JSP generation module, The controller generation module, the data persistence layer generation module and the configuration file generation module generate the Web background code, which improves the developer's efficiency in developing the workflow Web application system and improves the code quality.

Description of drawings

Figure 1a is a schematic diagram of the composition and structure of a code generation system according to an embodiment of the present invention;

FIG. 1b is a schematic diagram of the composition and structure of another code generation system according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of the implementation flow of a code generation method according to an embodiment of the present invention;

3 is a schematic diagram of a code generation system in a workflow system according to an embodiment of the present invention;

4 is a first schematic diagram of the application of the code generation system in the workflow Web development environment according to the embodiment of the present invention;

FIG. 5 is a second schematic diagram of the application of the code generation system in the workflow application environment according to the embodiment of the present invention;

6 is a schematic diagram of an implementation flow for reading a static form according to an embodiment of the present invention;

Fig. 7 is the realization flowchart of the generation front-end JSP view file of the embodiment of the present invention;

Fig. 8 is the realization flow diagram of the back-end code file of generation Hibernate persistent layer of the embodiment of the present invention;

Fig. 9 is the realization flowchart of the generation Struts2 control layer code file of the embodiment of the present invention;

FIG. 10 is a schematic diagram of an implementation flow of generating a Struts2XML configuration file according to an embodiment of the present invention.

detailed description

The basic idea of the present invention is: the actual project development cost is often concentrated in the development of business process modules, the processing of loopholes (Bugs) after project development is completed, the modification of codes after business changes, and the modified Bug processing and code testing. If a template-based method is adopted in code generation, users can design corresponding templates according to different architectures; in the workflow development environment, use the process definition language to design flow charts, and design each human task activity node through a static form designer For the static form used for human interaction, the code generation system reads and analyzes the code of the control of the static form to generate the target code.

The present invention will be described in further detail below in conjunction with the accompanying drawings and specific embodiments.

Figure 1a is a schematic diagram of the composition and structure of the code generation system of the embodiment of the present invention, as shown in Figure 1a, including:

The static form reading module 11 is used to read the code of the control of the static form, and determine the attribute of the control according to the code of the control of the static form; attribute, store the control object in the corresponding variable set;

The JSP generation module 12 is used to generate JavaScript codes corresponding to different attribute variable sets according to the attributes of the control object in the variable set, and generate a view layer JSP file according to the JavaScript code and the code of the control of the static form;

The data persistence layer generating module 13 is used to read the business data table corresponding to the form data operation, and generate POJO class files and DAO class files respectively corresponding to the names of the business data table according to the data structure of the business data table ;

The controller generation module 14 is used to generate the controller Java class file corresponding to the name of the static form according to the attributes of the control object in the variable set, and the instance of the POJO class file and the instance of the DAO class file , the controller Java class file includes: a controller Java class file for processing a form request and a controller Java class file for processing a form request;

The configuration file generating module 15 is configured to generate an XML configuration file, the attribute of the action node in the XML configuration file corresponds to the name of the static form.

Preferably, the JSP generation module is also used to generate an empty JSP file whose name is corresponding to the name of the static form; add an external CSS file and a static HTML tag in the JSP file; The code of the control is added to the body tag in the JSP file;

Determine the variable of the control that reads form data in the static form, generate the tag front-end code corresponding to the variable of the control that reads form data, and the JavaScript code that assigns a value to the variable of the control that reads form data, And write described JSP file; Determine the variable of the non-empty control that saves form data and the data that requires preservation in the described static form, generates the JavaScript code of verification form control legitimacy, and writes described JSP file;

Generating JavaScript codes for preventing repeated submission of form data and JavaScript codes for verifying the validity of the static form, and writing them into the JSP file.

Preferably, the data persistence layer generation module is also used to generate an empty POJO class file corresponding to the name of the business data table, obtain the field type and field name of the business data table, and send the POJO class file Write the attribute corresponding to the field type and field name of the business data table;

Generate an empty DAO class file corresponding to the name of the business data table, write the attribute corresponding to the field type and field name of the business data table to the DAO class file;

Instantiate the first string variable (StringBuilder), generate a source file that calls the basic operations of adding, deleting, modifying, and checking the Hibernate interface, write the source file into the first StringBuilder, and write the first StringBuilder Write the DAO class file.

Preferably, the controller generating module is further configured to generate an empty first controller Java class file for processing a request to view a form, and the name of the first controller Java class file corresponds to the name of the static form;

Instantiate the second StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the first controller Java class file, and generate the Java class file corresponding to the first controller An acquisition (getter) application and a setting (setter) application of the instance variable, adding the getter application and the setter application to the first StringBuilder;

Generate an execute application corresponding to the Java class file of the first controller class, and add the execute application to the first StringBuilder;

Adding the first StringBuilder to the first controller Java class file;

Generate an empty second controller Java class file for processing the submitted form request, the name of the second controller Java class file corresponds to the name of the static form;

Instantiate the third StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the second controller Java class file, and generate a getter application and a setter corresponding to the instance variable application, adding the getter application and the setter application to the third StringBuilder;

Generate an execute application corresponding to the Java class file of the second controller, and add the execute application to the third StringBuilder;

Add the third StringBuilder to the second controller Java class file.

The configuration file generation module is also used to generate an empty XML configuration file, and generates a corresponding package node and an action node corresponding to the static form name in the XML configuration file to generate an empty XML configuration file;

Instantiate the fourth StringBuilder, and add the statement of the XML configuration file to the fourth StringBuilder;

Generate the package node of the XML configuration file and the action node corresponding to the name of the static form, and add them to the fourth StringBuilder;

Write the fourth StringBuilder into the XML configuration file.

Fig. 1b is a schematic diagram of the composition structure of another code generating system according to the embodiment of the present invention, as shown in Fig. 1b, except including the above-mentioned static form reading module 11, JSP generating module 12, data persistence layer generating module 13, and controller generating module 14 and configuration file generating module 15, the system can also include:

The workflow engine 16 is used to schedule the JSP generation module 12 to generate the view layer JSP file, that is, the front-end code of the manual activity page of the Web application system; the scheduling data persistence layer generation module 13, the controller generation module 14 and the configuration file generation module 15 are correspondingly generated POJO class files and DAO class files, controller Java class files, and XML configuration files, that is, the Web background code of the manual activity page of the Web application system.

Fig. 2 is a schematic diagram of the implementation flow of the code generation method of the embodiment of the present invention, as shown in Fig. 2, including:

Step 201: Read the code of the control of the static form, determine the property of the control according to the code of the control of the static form; encapsulate the control into a control object, and convert the control object according to the property corresponding to the control object The control object is stored in the corresponding variable set;

Step 202: According to the attributes of the control objects in the variable set, generate JavaScript codes corresponding to different attribute variable sets, and generate a view layer JSP file according to the JavaScript codes and the codes of the controls of the static form;

In a preferred implementation of step 202, generate the empty JSP file whose name is corresponding to the name of the static form; Add the external CSS file and the static HTML tag in the JSP file; The code is added to the main body tag in the JSP file;

Determine the variable of the control that reads form data in the static form, generate the tag front-end code corresponding to the variable of the control that reads form data, and the JavaScript code that assigns a value to the variable of the control that reads form data, And write described JSP file; Determine the variable of the non-empty control that saves form data and the data that requires preservation in the described static form, generates the JavaScript code of verification form control legitimacy, and writes described JSP file;

Generate JavaScript codes to prevent repeated form submissions, and write them into the JSP file.

Step 203: read the business data table, and generate simple JAVA object POJO class files and data access object DAO class files respectively corresponding to the names of the business data table according to the data structure of the business data table;

In a preferred implementation of step 203, an empty POJO class file corresponding to the name of the business data table is generated, the field type and field name of the business data table are obtained, and the POJO class file is written to the POJO class file. The attributes corresponding to the field types and field names of the business data table;

Generate an empty DAO class file corresponding to the name of the business data table, write the attribute corresponding to the field type and field name of the business data table to the DAO class file;

Instantiate the first StringBuilder, generate the source file of the basic operation of adding, deleting, changing, and checking the object-relational mapping framework Hibernate interface of the open source code, write the source file into the first StringBuilder, and write the The first StringBuilder is written to the DAO class file.

Step 204: Generate a controller Java class file corresponding to the name of the static form according to the attributes of the control object in the variable set, and the instance of the POJO class file and the instance of the DAO class file, the controller The Java class file includes: a controller Java class file for processing a request to view a business data table and a controller Java class file for processing a request for submitting a business data table;

In a preferred implementation of step 204, generate an empty first controller Java class file for processing the form request, the name of the first controller Java class file corresponds to the name of the static form;

Instantiate the second StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the first controller Java class file, and generate the Java class file corresponding to the first controller The getter application and the setter application of the instance variable, adding the getter application and the setter application to the first StringBuilder;

Generate an execute application corresponding to the first controller class Java class file, and add the execute application to the first StringBuilder;

Adding the first StringBuilder to the first controller Java class file;

Generate an empty second controller Java class file for processing the submitted form request, the name of the second controller Java class file corresponds to the name of the static form;

Instantiate the third StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the second controller Java class file, and generate a getter application and a setter corresponding to the instance variable application, adding the getter application and the setter application to the third StringBuilder;

Generate an execute application corresponding to the Java class file of the second controller, and add the execute application to the third StringBuilder;

Add the third StringBuilder to the second controller Java class file.

Step 205: Generate an XML configuration file, the attribute of the action node in the XML configuration file corresponds to the name of the static form.

In a preferred implementation manner of step 205, an empty XML configuration file is generated, and a corresponding package node and an action node corresponding to the name of the static form are generated in the XML configuration file. Generate an empty XML configuration file;

Instantiate the fourth StringBuilder, and add the statement of the XML configuration file to the fourth StringBuilder;

Generate the package node of the XML configuration file and the action node corresponding to the name of the static form, and add them to the fourth StringBuilder;

Write the fourth StringBuilder into the XML configuration file.

The code generation method and system of the embodiment of the present invention will be further described below by taking the maintenance reporting system as an example and referring to FIGS. 3 to 5 .

Figure 3 is a schematic diagram of the location of the code generation system in the workflow system according to the embodiment of the present invention. The code generation system takes the properties of the controls of the static form of the repair system as input, and outputs the file of the target code required for the operation of the manual task node in the repair system, and finally saves the file of the target code to the location specified by the server.

Fig. 4 is a schematic diagram of the application of the code generation system in the workflow Web development environment according to the embodiment of the present invention. As shown in Fig. Design the static form and process definition file of the repair system required by the human task node of the repair system. Specifically: Double-click the manual task node in the workbench, select the static form corresponding to the node, and call the code generation system to generate the target code corresponding to the manual task node in the repair system, including JSP view files, POJO class files, DAO class files, Controller files and XML configuration files.

Fig. 5 is the second application diagram of the code generation system in the workflow application environment according to the embodiment of the present invention. After initiating the request to read the static form, the controller generation module 14 of the code generation system reads the business data stored in the repair service data table, and returns the generated front-end JSP view file to the user according to the result of data processing. The front-end JSP After the view file shows the business data to the user, the user can fill in the repair business data in the control of the static form to obtain the repair business data, and submit it to the background server of the repair system, and the data persistence layer generation module 13 of the code generation system will generate the repair business data Persist in the business database, and call the application program interface (API, ApplicationProgramInterface) provided by the workflow engine 16 to end the manual task node, so that the repair process continues to flow.

In the following, the manual activity node of website repair application in the heating repair repair system is taken as an example, and the code generation method of the embodiment of the present invention is further described in detail.

In order to initiate a website repair application manual activity node, a static form for human-computer interaction is visually designed, and the static form is named newApply. The static form includes 7 controls, which are the name of the repair person (attribute name="userName", type=" readnotNull", table="user", field="userName"), caller's fixed phone (attribute name="telephone", type="read", table="user", field="telephone"), caller's family Address (attribute name="address", type="readnotNull", table="user", field="address"), repairer's mobile phone (attribute name="mobile", type="readnotNull", table= "user", field="mobile"), the boiler room where the repairer's community is located (the attribute is name="ceilName", type="read", table="user", field="ceilName"), the type of repair report (the attribute is name="repairType", type="insert", table="repair", field="repairType"), repair content control (attribute name="repairDetail", type="insert", table="repair", field = "repairDetail").

Double-click the website repair application manual task node in the flow chart, select the website repair application form for the manual task node, and click OK to call the code generation system. Figure 6 is a schematic diagram of the implementation process of reading the static form in the embodiment of the present invention, as shown 6, including the following steps:

Step 601: cyclically read the controls in the static form of repair application;

Steps 602 to 603: determine the type of controls in the form, and classify different form controls according to the custom type attribute of the form controls;

type="read" indicates the form control for reading the data in the business data table. The data in the business data table includes the fixed telephone number of the repair applicant, the home address of the repair applicant, the mobile phone of the repair applicant, and the boiler room where the repair community is located; type="insert" indicates the acquisition of users Business data is written into the database form control, including two form controls of repair type and repair content; type="notNull" indicates a non-null type control, including the name of the repairer, home address and mobile phone. The value of the type attribute can be separated by spaces to represent multiple values. For example, if the repairer name control is both a control for reading the data type of the business data table and a control of a non-null type, then the corresponding type="readnotNull".

Step 604: Save objects corresponding to different types of form controls into corresponding control object variable sets;

Encapsulate the control of the form as an object, and the properties of the object are the properties of the corresponding control. For example, the object userName includes type, name, table and field properties, and save different types of controls into the corresponding control object variable collection. Specifically, the The object corresponding to the form control that reads the business data table data is stored in the variable set readSet of the read type, the object corresponding to the control of the non-null type is stored in the variable set notNullSet of the non-null type, and the control corresponding to the user business data is obtained The object is stored in the variable set insertSet of the write type.

Fig. 7 is a schematic diagram of the implementation process of generating a front-end JSP view file according to an embodiment of the present invention, as shown in Fig. 7, comprising the following steps:

Step 701: generate a JSP empty file;

The JSP empty file name corresponding to the human task node is newApply.JSP, and the file name corresponds to the static form name newApply.

Step 702: writing static part and hypertext markup language (HTML, HyperTextMarkupLanguage) tags to the JSP file;

Write the static part to newApply.JSP, including JSP head declaration <%pagelanguage="java"contentType="text/html; charset=UTF-8"pageEncoding="UTF-8"%> and HTML tag <html> <head><meta><body>.

Step 703: read the code of the static form and add it to the <body> tag in the JSP file;

Step 704: traverse and save the form control variables for reading business data table data in the variable set of the read type;

Traverse the form control variables that save and read the data type of the business data table, and generate Struts2 tag front-end code and JavaScript code for assigning values to the form control variables for these form control variables, such as varuserName=document.getElementById('userName'); userName.value= '<s:propertyvalue="user. userName"/>'.

Step 705: Generate Javascript code for verifying the legitimacy of the form control;

Traverse and save the form control variables that obtain user business data in the write type variable set, and generate Javascript code to verify the legitimacy of the form control for non-empty form control variables, such as the name of the repairer, home address, and mobile phone.

Step 706: Generate JavaScript codes to prevent repeated form submission;

Step 707: Generate JavaScript code for validating the static form;

Step 707: Write the above generated code into an empty JSP file to obtain a complete front-end JSP view file, and store it in the specified path /web/content/JSP.

Fig. 8 is the realization flowchart of the back-end code file that generates the Hibernate persistent layer of the embodiment of the present invention, as shown in Fig. 8, comprises the following steps:

Step 801: traverse all business data tables;

Obtain all business data tables of the heating repair system such as user and repair through Jdbc, and traverse all business data tables.

Step 802: Obtain the data structure of the business data table;

Including information such as the name of the business data table, field type, and field name.

Step 803: Generate a POJO persistent class file with the same name as the business data table;

Including User and Repair.

Step 804: traverse all fields of the business data table;

Step 805: Write the member variable corresponding to the field into the POJO persistent class file;

Step 806: Generate Java-type attribute variables corresponding to field names and types in the business data table, and write these attributes into the POJO class file.

Step 807: Generate POJO class files and DAO class files.

The generated files are stored to the specified path /src/com/model/.

Generate an empty data access object Java class (DAO) according to the name of the business data table, such as UserDAO, RepairDAO, and instantiate an empty Java variable string class source code variable StringBuilder, which is used to save the DAO class source code, and store the business data table user, The POJO class User and Repair corresponding to repair are respectively used as the attributes user and repair of the DAO class UserDAO and RepairDAO to generate the source code for the basic operation of adding, deleting, modifying and checking the Hibernate interface, and add these source codes to the source code variable to save the DAO class. Write the StringBuilder variable data of the source code into an empty DAO file, generate the final DAO class file, and put the generated file in the specified path /src/com/DAO/.

Fig. 9 is the realization flowchart of the generation Struts2 control layer code file of the embodiment of the present invention, as shown in Fig. 9, comprises the following steps:

Step 901: Obtain all business data tables user and repair of the heating repair reporting system, and loop through all business data tables;

Step 902: generating the first Struts2 controller empty Java class file;

Generate the first empty Java class file of the Struts2 controller for processing the user's request to view the business form, and the name of the file corresponds to the name of the static form, such as ApplyFirstAction.

Step 903: instantiate the variable StringBuilder of the source code of the first Struts2 controller class file;

Instantiate the variable string source code variable StringBuilder used to save the first Struts2 controller class file.

Step 904: Generate getter and setter applications of instance variables and add them to StringBuilder;

Use the DAO persistent class instance and POJO class instance corresponding to the business table as the instance variable of the controller class. For example, the class ApplyFirst contains variable attributes of User and UserDao types, generate getter and setter applications for these control variables, and add them to Character variable StringBuilder.

Step 905: Generate the execute application of the first Struts2 controller class and add it to StringBuilder;

Generate the execute application of the first Struts2 controller class, call the query interface of the DAO class instance inside the method, such as user=userDao.get(), and call the API of the workflow engine, and add the method body to the StringBuilder variable.

Step 906: Generate the final first Struts2action file and place it in the specified path /src/com/action/;

Write the source code variable of the first Struts2action into the empty file of the first sturts2action, generate the final first Struts2action file, and place the file in the specified path /src/com/action/.

Step 907: Generate a second Struts2 controller empty Java class file;

Generate an empty Java class file for the second Struts2 controller. The name of the file is based on the name of the form, such as ApplySecondAction.

Step 908: Instantiate the variable StringBuilder that saves the source code of the second Struts2 controller class file;

Step 909: Generate getter and setter applications of instance variables and add them to StringBuilder;

Use the DAO persistent class instance and POJO class instance corresponding to the business table as the instance variable of the controller class, generate getter and setter applications of these instance variables, and add them to StringBuilder.

Step 910: Generate the execute application of the second Struts2 controller class and add it to StringBuilder;

Generate the execute application of the second Struts2 controller class, call the persistent interface of the DAO class instance such as repairDao.add(repair) inside the application, and call the API of the workflow engine to add the application body to StringBuilder.

Step 911: Generate the final second Struts2action file.

Write the source code variable of the second Struts2action into the empty file of the second struts2action to generate the final second Struts2action file, and place the file in the specified path /src/com/action.

Fig. 10 is a schematic diagram of the implementation process of generating a Struts2XML configuration file according to an embodiment of the present invention, as shown in Fig. 10 , comprising the following steps:

Step 1001: generating an empty Struts2XML configuration file;

The file name is struts.XML.

Step 1002: instantiate variable StringBuilder;

Source code for saving Struts2XML configuration files.

Step 1003: Add the declaration of the XML configuration file to StringBuilder;

Step 1004: Generate the package node of the XML configuration file and add it to StringBuilder;

Step 1005: generate an action node according to the static form;

The attribute name and class of the action node are based on the name of the static form, such as <actionname="applyFirst"class="com.action.ApplyFistAction>" and <actionname="applySecond"class="ApplySecondAction">;

Write the data in the source variable into the empty XML configuration file, generate the final XML configuration file, and place it in the specified path.

Step 1004: generating an action node and assigning attribute values;

Action nodes are generated according to the static form, and the attribute name and class of the action node are based on the name of the static form, such as <actionname="applyFirst"class="com.action.ApplyFistAction>" and <actionname="applySecond"class="ApplySecondAction"> .

Write the data in the source variable into the empty XML configuration file, generate the final XML configuration file, and place it in the specified path.

According to the target file generated above, deploy the process definition and initiate the process instance for human-computer interaction.

The code generation process of other manual task node acceptors reviewing applications, on-duty managers dispatching maintenance personnel, on-duty manager uploading maintenance results, and accepting personnel's telephone return visits will all generate front-end JSP view files and background controller StrutsAction files corresponding to the manual task nodes. , POJO file, DAO file, and add the actiondom node corresponding to the human task node to the struts.xml configuration file.

The code generation system recorded in the embodiment of the present invention can be installed and deployed in the form of a popular development tool Eclipse plug-in. The user only needs to copy the plug-in to the directory of the corresponding development tool, and select it in the corresponding project to perform auxiliary code generation. Shorten the development cycle of developers and improve development efficiency;

Moreover, the code generation system recorded in the embodiments of the present invention has made innovations in code generation for business logic. For example, developers only need to visually design static forms through the form designer and set various custom forms for form controls. attribute, you can generate code that conforms to the relevant business logic. All codes generated by the code generation system are based on templates. Templates can be configured according to the different needs of the company, so that the automatic generation of codes can be customized, and the code availability, code generation quality and code generation efficiency are all obtained. greatly improved.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (10)

1. A code generation system, characterized in that the system comprises: The static form reading module is used to read the code of the control of the static form, and determine the attribute of the control according to the code of the control of the static form; the control is encapsulated as a control object, and according to the corresponding attribute, storing the control object in a corresponding variable set; The Java server page JSP generation module is used to generate JavaScript codes corresponding to different attribute variable sets according to the attributes of the control objects in the variable set, and generate the view layer JSP file according to the JavaScript codes and the codes of the controls of the static form ; The data persistence layer generation module is used to read the business data table corresponding to the form data operation, and according to the data structure of the business data table, generate a simple JAVA object POJO class file corresponding to the name of the business data table and data Access object DAO class file; A controller generation module, configured to generate a controller Java class file corresponding to the name of the static form according to the attributes of the control object in the variable set, and the instance of the POJO class file and the instance of the DAO class file, Described controller Java class file comprises: the controller Java class file of processing viewing form request and the controller Java class file of processing submission form request; The configuration file generation module is configured to generate an Extensible Markup Language XML configuration file, the attribute of the action node in the XML configuration file corresponds to the name of the static form. 2. The system of claim 1, wherein: The JSP generation module is also used to generate the empty JSP file corresponding to the name of the static form; add an external cascading style sheet CSS file, a static hypertext markup language HTML tag in the JSP file; The code of the control of the static form is added to the main body tag in the JSP file; Determine the variable of the control that reads form data in the static form, generate the tag front-end code corresponding to the variable of the control that reads form data, and the JavaScript code that assigns a value to the variable of the control that reads form data, And write described JSP file; Determine the variable of the non-empty control that saves form data and the data that requires preservation in the described static form, generates the JavaScript code of verification form control legitimacy, and writes described JSP file; Generate JavaScript codes to prevent repeated form submissions, and write them into the JSP file. 3. The system of claim 1, wherein: The data persistence layer generation module is also used to generate an empty POJO class file corresponding to the name of the business data table, obtain the field type and field name of the business data table, and write the POJO class file to the POJO class file. The attributes corresponding to the field type and field name of the business data table; Generate an empty DAO class file corresponding to the name of the business data table, write the attribute corresponding to the field type and field name of the business data table to the DAO class file; Instantiate the first string variable StringBuilder, generate the source file that calls the basic operation of adding, deleting, changing, and checking the Hibernate interface, write the source file into the first StringBuilder, and write the first StringBuilder into the The DAO class file. 4. The system of claim 3, wherein: The controller generation module is also used to generate an empty first controller Java class file for processing viewing form requests, and the name of the first controller Java class file is corresponding to the name of the static form; Instantiate the second StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the first controller Java class file, and generate the Java class file corresponding to the first controller Obtaining the getter application and setting the setter application of the instance variable, adding the getter application and the setter application to the first StringBuilder; Generate an execute application corresponding to the first controller class Java class file, and add the execute application to the first StringBuilder; Adding the first StringBuilder to the first controller Java class file; Generate an empty second controller Java class file for processing the submitted form request, the name of the second controller Java class file corresponds to the name of the static form; Instantiate the third StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the second controller Java class file, and generate a getter application and a setter corresponding to the instance variable application, adding the getter application and the setter application to the third StringBuilder; Generate an execute application corresponding to the Java class file of the second controller, and add the execute application to the third StringBuilder; Add the third StringBuilder to the second controller Java class file. 5. The system according to any one of claims 1 to 4, characterized in that, The configuration file generation module is also used to generate an empty XML configuration file, and generates a corresponding package node and an action node corresponding to the static form name in the XML configuration file to generate an empty XML configuration file; Instantiate the fourth StringBuilder, and add the statement of the XML configuration file to the fourth StringBuilder; Generate the package node of the XML configuration file and the action node corresponding to the name of the static form, and add them to the fourth StringBuilder; Write the fourth StringBuilder into the empty XML configuration file. 6. A code generation method, characterized in that the method comprises: Read the code of the control of the static form, determine the property of the control according to the code of the control of the static form; encapsulate the control into a control object, and store the control object according to the property corresponding to the control object to the corresponding variable set; Generate JavaScript codes corresponding to different attribute variable sets according to the attributes of the control objects in the variable set, and generate a view layer JSP file according to the JavaScript codes and the codes of the controls of the static form; Read the business data table, according to the data structure of the business data table, generate the simple JAVA object POJO class file and the data access object DAO class file corresponding to the name of the business data table respectively; According to the attribute of the control object in the variable set, and the instance of the POJO class file and the instance of the DAO class file, generate a controller Java class file corresponding to the name of the static form, and the controller Java class file Including: the controller Java class file that handles the request to view the form and the controller Java class file that handles the request to submit the form; An XML configuration file is generated, and the attribute of the action node in the XML configuration file corresponds to the name of the static form. 7. The method according to claim 6, wherein, according to the attributes of the control objects in the variable set, JavaScript codes corresponding to different attribute variable sets are generated, and according to the JavaScript code and the controls of the static form The code generates the view layer JSP file, including: Generate an empty JSP file whose name corresponds to the name of the static form; add an external CSS file and a static HTML tag in the JSP file; add the code of the control of the static form to the body in the JSP file inside the label; Determine the variable of the control that reads form data in the static form, generate the tag front-end code corresponding to the variable of the control that reads form data, and the JavaScript code that assigns a value to the variable of the control that reads form data, And write into described JSP file; Determine the variable of the non-empty control that saves form data and the data that requires preservation in described static form, generates the JavaScript code that verifies form control legitimacy, and writes into described JSP file; Generate JavaScript codes to prevent repeated form submissions, and write them into the JSP file. 8. The method according to claim 6, characterized in that, the read service data table, according to the data structure of the service data table, generates POJO class files corresponding to the title of the service data table respectively, and Data Access Object DAO class files, including: Generate an empty POJO class file corresponding to the name of the business data table, obtain the field type and field name of the business data table, and write the field type and field name of the business data table to the POJO class file corresponding attributes; Generate an empty DAO class file corresponding to the name of the business data table, write the attribute corresponding to the field type and field name of the business data table to the DAO class file; Instantiate the first StringBuilder, generate the source file for the basic operations of adding, deleting, modifying, and checking the Hibernate interface, write the source file into the first StringBuilder, and write the first StringBuilder into the DAO class files. 9. The method according to claim 8, characterized in that, according to the attribute of the control object in the variable concentration, and the instance of the POJO class file and the instance of the DAO class file, the static form is generated The name corresponds to the controller Java class file, including: Generate an empty first controller Java class file for processing viewing form requests, the name of the first controller Java class file corresponds to the name of the static form; Instantiate the second StringBuilder, use the instance variable of the DAO class file and the POJO class file corresponding to the business data table as the instance variable of the first controller Java class file, and generate the Java class file corresponding to the first controller The getter application and the setter application of the instance variable, adding the getter application and the setter application to the first StringBuilder; Generate an execute application corresponding to the first controller class Java class file, and add the execute application to the first StringBuilder; Adding the first StringBuilder to the first controller Java class file; Generate an empty second controller Java class file for processing the submitted form request, the name of the second controller Java class file corresponds to the name of the static form; Instantiate the third StringBuilder, use the instance of the DAO class file corresponding to the business data table and the instance of the POJO class file as the instance variable of the second controller Java class file, and generate a getter application and a setter corresponding to the instance variable application, adding the getter application and the setter application to the third StringBuilder; Generate an execute application corresponding to the Java class file of the second controller, and add the execute application to the third StringBuilder; Add the third StringBuilder to the second controller Java class file. 10. The method according to any one of claims 6 to 9, wherein the generating XML configuration file, the attribute of the action node in the XML configuration file corresponds to the name of the static form, includes: Generate an empty XML configuration file, generate a corresponding package node and an action node corresponding to the static form name in the XML configuration file, and generate an empty XML configuration file; Instantiate the fourth StringBuilder, and add the statement of the XML configuration file to the fourth StringBuilder; Generate the package node of the XML configuration file and the action node corresponding to the name of the static form, and add them to the fourth StringBuilder; Write the fourth StringBuilder into the empty XML configuration file.