CN111913695A - Code conversion method, device and storage medium - Google Patents

Abstract

The invention provides a code conversion method, device and storage medium. The method can complete functional page construction in a page construction unit, generate a page structure XML file, parse the page structure XML file to generate a page structure XML source code, and according to the business system The front-end technical architecture requires that the parsing result be converted into the front-end framework source code corresponding to the first target framework template. Use the obtained second target framework template to convert the data access model binding information in the page structure XML source code, and use the file generator to process the converted data access model binding information to generate the back-end business logic source code, so as to achieve The purpose of improving the quality of code development and reducing the technical difficulty of development.

Description

A code conversion method, device and storage medium

technical field

The present invention relates to the technical field of computers, in particular to a code conversion method, device and storage medium.

Background technique

With the continuous improvement of the level of social informatization, the competition in the information industry has become more and more fierce, and the government and enterprises have put forward higher requirements for the development of informatization application systems. The changing demand has become a hot research topic in the industry, and it is also a problem that page construction tools need to solve urgently.

SUMMARY OF THE INVENTION

In view of this, embodiments of the present invention provide a code conversion method, device, and storage medium, so as to improve the quality of code development and reduce the technical difficulty of development.

To achieve the above purpose, the embodiments of the present invention provide the following technical solutions:

A code conversion method including:

Obtain the page structure XML file generated according to the business function interface;

Use an XML file parser to parse the page structure XML file to obtain the page structure XML source code of the page structure XML file;

Obtain the first target framework template in the front-end framework template library;

Converting page elements and operation events in the page structure XML source code based on the first target frame template to obtain the front-end frame source code;

Obtain the data access model binding information bound in the page structure XML source code;

Obtain the second target framework template from the back-end framework template library;

Using the mapping relationship stored in the second target framework template, data conversion is performed on the data access model binding information;

The file generator is used to process the converted data access model binding information, and the back-end business logic source code is obtained.

Optionally, in the above code conversion method, the obtaining of the page structure XML file generated according to the business function interface is specifically:

The functional interface constructed by the page builder is acquired, and the functional interface is stored in the form of an XML file to obtain a page structure XML file.

Optionally, in the above code conversion method, the page structure XML source code includes but is not limited to: page elements, operation events, and data access model binding information.

Optionally, in the above code conversion method, the page elements and operation events in the page structure XML source code are converted based on the first target frame template, and the page structure XML source code of the page structure XML file is obtained, specifically: for:

Taking the page elements and operation events as standard model information, instantiating a conversion engine according to the standard model information, and using the first target framework template to convert the standard model information after the instantiating the conversion engine to obtain a framework front end The model object information of the structure, based on the model object information, the file generation engine is called to obtain the page structure XML source code of the page structure XML file.

A code conversion device, comprising:

The page construction unit is used for the page structure XML file generated according to the business function interface;

A source code conversion unit, used for obtaining the page structure XML file generated according to the business function interface; using an XML file parser to parse the page structure XML file to obtain the page structure XML source code of the page structure XML file;

a file generation unit, used for obtaining the first target frame template in the front-end frame template library; converting the page elements and operation events in the page structure XML source code based on the first target frame template to obtain the front-end frame source code; Obtain the data access model binding information bound in the XML source code of the page structure; obtain the second target frame template from the back-end frame template library; use the mapping relationship stored in the second target frame template to The data access model binding information is used for data conversion; the file generator is used to process the converted data access model binding information, and the back-end business logic source code is obtained.

Optionally, in the above code conversion device, the page construction unit is specifically used for:

The functional interface constructed by the page builder is acquired, and the functional interface is stored in the form of an XML file to obtain a page structure XML file.

Optionally, in the above code conversion apparatus, the page structure XML source code includes but is not limited to: page elements, operation events, and data access model binding information.

Optionally, in the above code conversion device, the file generation unit converts the page elements and operation events in the page structure XML source code based on the first target frame template, and obtains the page structure XML file. When the page structure XML source code is used, it is specifically used for:

Taking the page elements and operation events as standard model information, instantiating a conversion engine according to the standard model information, and using the first target frame template to convert the standard model information after the instantiating the conversion engine to the model of the front-end structure of the framework Object information, calling a file generation engine based on the model object information to obtain the page structure XML source code of the page structure XML file.

A storage medium, the storage medium stores a plurality of instructions, the instructions are suitable for being loaded by a processor to execute the steps in the code conversion method described in any one of the above.

Based on the above technical solutions, the above solutions provided by the embodiments of the present invention can complete functional page construction in a page construction unit, generate a page structure XML file, parse the page structure XML file to generate a page structure XML source code, according to the front end of the business system The technical framework requires that the parsing result be converted into the front-end framework source code corresponding to the first target framework template. Use the acquired second target framework template to convert the data access model binding information in the page structure XML source code, and use the file generator to process the converted data access model binding information to generate the back-end business logic source code, so as to achieve The purpose of improving the quality of code development and reducing the technical difficulty of development.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention. For those of ordinary skill in the art, other drawings can also be obtained according to the provided drawings without creative work.

Fig. 1 is the schematic flow chart of the code conversion method that this application embodiment provides;

FIG. 2 is a schematic structural diagram of a code conversion apparatus disclosed in an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

In view of the problems existing in these page construction tools, the present invention proposes a method and device for converting front-end and back-end codes based on page models. In the page builder, business functions are constructed according to the user's macro requirements, and business standardization is continuously improved to form a complex Using the page template, through the source code conversion device, the page model generates the front-end and back-end source code according to the selected technical framework, which improves the development quality and reduces the development difficulty.

In order to solve the above problems raised in the background art, the present invention provides a method and apparatus for converting front-end and back-end codes based on a page model. The method can complete the function page construction in the page construction unit, generate the page structure XML source code, and then parse the page structure XML source code through the source code conversion unit, and convert the analysis result into the corresponding front-end framework according to the front-end technical framework requirements of the business system The source code, the supported front-end framework, can also be added, expanded or upgraded with the development of technology. The back-end logic source code converts the corresponding microservice or traditional MVC framework source code according to the data access model binding information bound in the page structure XML source code. In the conversion process, according to the page structure XML source code event binding information, the generated logic interface is bound to the front-end operation event, without the need for secondary development, to generate a complete runnable function source code. In order to achieve the purpose of improving the quality of code development and reducing the technical difficulty of development.

Specifically, referring to FIG. 1 , the code conversion method disclosed in the embodiment of the present application includes:

Step S101: obtaining a page structure XML file generated according to the business function interface;

In this step, when acquiring the page structure XML file, a page structure unit (page builder) can be used to generate it. Specifically, when this method is executed, the page structure unit is first triggered, and after the page structure unit is triggered, Through the functional interface constructed by the page builder, the functional interface is stored in the form of an XML file to obtain a page structure XML file. Wherein, the functional interface constructed by the page builder is a functional interface obtained by the page builder creating a new page according to business requirements, or selecting an adapted function from a template library to add or maintain an already constructed page. The construction unit constructs a new functional interface and stores it as an XML file. The so-called page construction is a visual and WYSIWYG software construction method.

Step S102: using an XML file parser to parse the page structure XML file to obtain the page structure XML source code of the page structure XML file;

In this step, the page structure XML file is parsed by triggering the XML file parser. In this process, the XML file parser takes the page structure XML file as input information, parses the page structure XML file, and obtains Page structure XML source code, the page structure XML source code includes but is not limited to: page elements, operation events, and data access model binding information, and page elements, operation events and data access model binding information are separated from the page structure XML source code. After determining the information, the conversion engine is instantiated according to the information. The instantiating conversion engine refers to the method of separating the process of object creation and use through the factory pattern, and providing the same interface, thereby reducing code duplication.

The data access model information refers to the model of the set of business data items, which is obtained by generating a SQL statement query through the relationship between the objects of the data physical model.

Step S103: obtaining the first target frame template in the front-end frame template library;

In the technical solutions disclosed in the embodiments of the present application, a front-end framework template library and a back-end framework template library are pre-established, and the front-end framework template library and the back-end framework template library store multiple sets of target framework templates. A standard software unit of a certain technical architecture can exist alone or can be expanded and assembled. These framework modules are front-end framework page element set templates and back-end business logic code structure templates that are customized in advance according to the conversion rules in the conversion device. When in use, those skilled in the art can customize the matching mapping rules in the above target frame templates according to user requirements, and can manage the target frame templates in a unified manner. To meet the development needs of the project team, to further improve business standardization and template reuse.

It not only realizes flexible template matching and mapping during the conversion process, but also manages template information in a unified manner. In the state of continuous innovation of front-end and back-end technologies, template information can be added or expanded in real time to meet the development needs of the project team, thereby further improving business standardization and efficiency. Template reuse.

In this step, according to the technical framework requirements of the actual business system, template information corresponding to the technical framework requirements can be obtained from the front-end framework template library, and the template is recorded as the first target framework template (MX, MVVM, VUE, React, etc.);

Step S104: converting the page elements and operation events in the page structure XML source code based on the first target framework template to obtain the front-end framework source code;

In this solution, through the template matching mapping relationship stored in the first target framework template, the page structure XML source code is converted into data, and the file generator is called to process the converted page structure XML source code, so as to generate a front-end display frame source;

During specific conversion: take the page elements and operation events as standard model information, instantiate a conversion engine for the standard model information, and use the first target framework template to convert the standard model information after the instantiated conversion engine The conversion is performed to obtain model object information of the front-end structure of the framework, and a file generation engine is invoked based on the model object information to obtain the page structure XML source code of the page structure XML file.

Step S105: acquiring the data access model binding information bound in the page structure XML source code;

In obtaining the end business logic source code, the data access model binding information bound in the page structure XML source code is required, that is, the data access model binding information above;

The data access model binding information binding is constructed from the business function data physical model entity object, which contains the relationship information between the data entities and the entities. After parsing the page structure XML file, sorting and merging the data access model binding information and the operation information corresponding to the data access model binding information, a complete data model and a collection of operations can be obtained, and then a standard model can be generated information.

Step S106: obtaining the second target framework template from the back-end framework template library;

In this step, according to the technical architecture requirements of the actual business system, template information corresponding to the technical framework requirements (such as microservices, single architecture OSGI, etc.) can be obtained from the back-end framework template library, and this template is recorded as the second a target framework template, where the second target framework template stores a mapping relationship between data access model binding information and model object information;

Step S107: Using the mapping relationship stored in the second target framework template, perform data conversion on the data access model binding information;

In this step, the data access model binding information is converted into corresponding model object information by using the second target framework template.

Further, the second target framework template may store the mapping relationship between standard model information and model object information. Therefore, in this solution, the second target framework template may be used to generate the standard model information. Mapping is performed to obtain the corresponding model object information.

Step S108: use the file generator to process the converted data access model binding information, and obtain the back-end business logic source code;

In this step, based on the converted model object information, a file generation engine is invoked to generate a functional back-end source code file corresponding to the model object information, and the source code file is the back-end business logic source code.

The above solutions disclosed in the embodiments of the present application can use an XML file parser to separate the page structure information in the self-defined page structure XML file, and complete the source code generation by using different target framework template matching and mapping, and realize the same set of page structure XML files. , which can convert multiple frameworks according to different technical architecture requirements, improve page template reuse, and reduce development difficulty.

Two template libraries of front-end and back-end are provided, and the first target frame template and the second target frame template are customized according to the conversion rules in the conversion device. It not only realizes flexible template matching and mapping during the conversion process, but also manages template information in a unified manner. In the state of continuous innovation of front-end and back-end technologies, template information can be added or expanded in real time to meet the development needs of the project team, thereby further improving business standardization and efficiency. Template reuse.

This embodiment discloses a code conversion device. For the specific work content of each unit in the device, please refer to the content of the above method embodiment. The code conversion device provided by the embodiment of the present invention is described below. The transcoding methods described above may refer to each other correspondingly.

Referring to FIG. 2 , a code conversion apparatus disclosed in an embodiment of the present application may include:

The page construction unit 100 is used for the page structure XML file generated according to the business function interface;

The source code conversion unit 200 is used to obtain the page structure XML file generated according to the business function interface; adopt an XML file parser to parse the page structure XML file to obtain the page structure XML source code of the page structure XML file;

The file generation unit 300 is used to obtain the first target frame template in the front-end frame template library; based on the first target frame template, the page elements and operation events in the page structure XML source code are converted to obtain the front-end frame source code Obtain the data access model binding information bound in the XML source code of the page structure; obtain the second target frame template from the back-end frame template library; adopt the mapping relationship stored in the second target frame template, to The data access model binding information is described for data conversion; the file generator is used to process the converted data access model binding information, and the back-end business logic source code is obtained.

Corresponding to the above method, the page construction unit is specifically used for:

The functional interface constructed by the page builder is acquired, and the functional interface is stored in the form of an XML file to obtain a page structure XML file.

Corresponding to the above method, the page structure XML source code includes but is not limited to: page elements, operation events, and data access model binding information.

Corresponding to the above method, the file generation unit converts page elements and operation events in the page structure XML source code based on the first target frame template, and obtains the page structure XML source code of the page structure XML file. , specifically for:

Taking the page elements and operation events as standard model information, instantiating a conversion engine according to the standard model information, and using the first target frame template to convert the standard model information after the instantiating the conversion engine to the model of the front-end structure of the framework Object information, calling a file generation engine based on the model object information to obtain the page structure XML source code of the page structure XML file.

The present application also discloses a storage medium, the storage medium stores a plurality of instructions, and the instructions are suitable for the processor to load, so as to execute the steps in the code conversion method described in any one of the above-mentioned methods of the present application.

For the convenience of description, when describing the above system, the functions are divided into various modules and described respectively. Of course, when implementing the present invention, the functions of each module may be implemented in one or more software and/or hardware.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for related parts. The systems and system embodiments described above are only illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, It can be located in one place, or it can be distributed over multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. Those of ordinary skill in the art can understand and implement it without creative effort.

Professionals may further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two, in order to clearly illustrate the possibilities of hardware and software. Interchangeability, the above description has generally described the components and steps of each example in terms of function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

The steps of a method or algorithm described in conjunction with the embodiments disclosed herein may be directly implemented in hardware, a software module executed by a processor, or a combination of the two. The software module can be placed in random access memory (RAM), internal memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other in the technical field. in any other known form of storage medium.

It should also be noted that in this document, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply those entities or operations There is no such actual relationship or order between them. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

The above description of the disclosed embodiments enables any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (9)

1. A method of transcoding, comprising:

acquiring a page structure XML file generated according to a service function interface;

adopting an XML file parser to parse the page structure XML file to obtain a page structure XML source code of the page structure XML file;

acquiring a first target frame template in a front-end frame template library;

converting the page elements and the operation events in the XML source code of the page structure based on the first target frame template to obtain a front-end frame source code;

acquiring data access model binding information bound in the XML source code of the page structure;

acquiring a second target frame template from the rear-end frame template library;

performing data conversion on the data access model binding information by adopting a mapping relation stored in the second target frame template;

and processing the converted data access model binding information by adopting a file generator to obtain a back-end service logic source code.

2. The transcoding method of claim 1, wherein the obtaining of the page structure XML file generated according to the service function interface specifically comprises:

and acquiring a functional interface constructed by a page constructor, and storing the functional interface in an XML file mode to obtain a page structure XML file.

3. The transcoding method of claim 1, wherein the page structure XML source code includes but is not limited to: page elements, operational events, and data access model binding information.

4. The code conversion method according to claim 2, wherein the page element and the operation event in the page structure XML source code are converted based on the first target frame template to obtain the page structure XML source code of the page structure XML file, and specifically, the method comprises:

and instantiating a conversion engine according to the standard model information by using the page elements and the operation events as standard model information, converting the standard model information after the instantiated conversion engine by using the first target frame template to obtain model object information of a frame front end structure, calling a file generation engine based on the model object information to obtain a page structure XML source code of the page structure XML file.

5. A transcoding apparatus, comprising:

the page construction unit is used for generating a page structure XML file according to the service function interface;

the source code conversion unit is used for acquiring a page structure XML file generated according to the service function interface; adopting an XML file parser to parse the page structure XML file to obtain a page structure XML source code of the page structure XML file;

the file generation unit is used for acquiring a first target frame template in the front-end frame template library; converting the page elements and the operation events in the XML source code of the page structure based on the first target frame template to obtain a front-end frame source code; acquiring data access model binding information bound in the XML source code of the page structure; acquiring a second target frame template from the rear-end frame template library; performing data conversion on the data access model binding information by adopting a mapping relation stored in the second target frame template; and processing the converted data access model binding information by adopting a file generator to obtain a back-end service logic source code.

6. The transcoding device of claim 5, wherein the page construction unit is specifically configured to:

and acquiring a functional interface constructed by a page constructor, and storing the functional interface in an XML file mode to obtain a page structure XML file.

7. The apparatus of claim 5, wherein the page structure XML source code includes but is not limited to: page elements, operational events, and data access model binding information.

8. The apparatus according to claim 6, wherein the file generating unit, when converting the page elements and the operation events in the page structure XML source code based on the first target frame template to obtain the page structure XML source code of the page structure XML file, is specifically configured to:

and taking the page elements and the operation events as standard model information, instantiating a conversion engine according to the standard model information, calling a file generation engine based on the model object information to generate model object information of a front end structure of a standard model information conversion frame after the conversion engine is instantiated by adopting the first target frame template, and obtaining a page structure XML source code of the page structure XML file.

9. A storage medium storing a plurality of instructions, the instructions adapted to be loaded by a processor,

to perform the steps in the transcoding method of any of claims 1 to 5.

Images