Method for generating input and output parameter entity in enterprise software upgrading and related equipment thereof

Abstract

The invention relates to the technical field of software upgrading and maintenance, and provides a method for generating an in-out parameter entity in enterprise software upgrading and related equipment thereof, and the method comprises the following steps: receiving an upgrading and maintenance request triggered by all front ends for operating software to be upgraded, copying upgrading and maintenance request data to a development environment for analysis; the method comprises the following steps: analyzing an entity in software to be upgraded to generate a corresponding input parameter entity, analyzing the entity and a corresponding method of the entity in the software to be upgraded, obtaining a Mapper proxy object set for the entity and a Mapper proxy object method set for the corresponding method of the entity, and executing methods in the Mapper proxy object method set through a reflection mechanism to obtain feedback information of a database. And generating a parameter-out entity corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the feedback information, thereby reducing the upgrading and maintenance cost of the enterprise-level software project and improving the upgrading and maintenance efficiency of the enterprise-level software project.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software upgrade maintenance, more particularly to a method for generating in-and-out parameter entities in enterprise software upgrade and related equipment thereof. BACKGROUND

[0002] In the development and maintenance process of enterprise-level software, its life cycle is often quite long, accompanied by numerous demand changes, mainly due to the high complexity of enterprise-level software and its close connection with the daily business operation of the enterprise. Any minor adjustment in business can trigger changes in software requirements and code. In this case, the upgrade and maintenance of old enterprise-level software projects are mainly achieved through table structure reverse code generation technology and MAP set receiving parameter and return parameter technology. However, when using table structure reverse code generation technology, the coverage of the generated entity class and interface method is low, and the matching rate of the generated entity class and the specific fields in the MAP is very low, which does not meet the expectation of reducing workload in upgrade and maintenance. In addition, when using MAP set receiving parameter and return parameter, although it can bring rapid demand response and less code changes in the early stage of project operation. However, with the iterative development of the project, it leads to uncontrolled demand disorder, low code quality, and poor readability. This results in a sharp increase in labor costs, low work efficiency, and decreased market competitiveness of products.

[0003] In summary, the existing upgrade and maintenance technology of enterprise-level software projects has the technical problems of high upgrade and maintenance cost and low efficiency. SUMMARY

[0004] The technical problem to be solved by the present application is to provide a method for generating in-and-out parameter entities in enterprise software upgrade and related equipment thereof to reduce the upgrade and maintenance cost of enterprise-level software projects and improve the upgrade and maintenance efficiency of enterprise-level software projects.

[0005] In a first aspect, the present application provides a method for generating in-and-out parameter entities in enterprise software upgrade, comprising the following steps:

[0006] Receiving all upgrade and maintenance requests triggered by front-end operations on the software to be upgraded, copying the upgrade and maintenance request data to the development environment for analysis to generate corresponding in-parameter entities;

[0007] Analyzing the entities in the software to be upgraded and the corresponding methods of the entities, obtaining a set of Mapper proxy objects for the entities and a set of Mapper proxy object methods for the corresponding methods of the entities;

[0008] By the reflection mechanism, the method in the Mapper proxy object method set is executed to obtain the feedback information of the database, and the out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set is generated according to the feedback information.

[0009] Further, receiving all front-end operation trigger upgrade maintenance requests for the software to be upgraded, including: receiving all front-end upgrade maintenance requests sent after clicking on the page of the software to be upgraded.

[0010] Further, copying the upgrade maintenance request data to the development environment for analysis to generate the corresponding input parameter entity, including:

[0011] Setting a request parameter filter, the request parameter filter is used to capture all the upgrade maintenance requests;

[0012] Saving all the upgrade maintenance requests captured by the request parameter filter to the MAP;

[0013] Converting all the upgrade maintenance requests saved in the MAP into JSON files, and copying the JSON files from the test environment to the local development environment for analysis to generate the corresponding input parameter entity.

[0014] Further, saving all the upgrade maintenance requests captured by the request parameter filter to the MAP, including:

[0015] Corresponding the URL of all the upgrade maintenance requests to the key of the MAP, and corresponding the request parameters of all the upgrade maintenance requests to the value of the MAP;

[0016] Saving the key of the MAP corresponding to the URL of all the upgrade maintenance requests to the MAP, and saving the value of the MAP corresponding to the request parameters of all the upgrade maintenance requests to the MAP.

[0017] Further, saving the key of the MAP corresponding to the URL of all the upgrade maintenance requests to the MAP, and saving the value of the MAP corresponding to the request parameters of all the upgrade maintenance requests to the MAP, including:

[0018] Judging whether the URLs of all the upgrade maintenance requests exist duplication, if not, saving the key of the MAP corresponding to the URL of all the upgrade maintenance requests to the MAP, and saving the value of the MAP corresponding to the request parameters of all the upgrade maintenance requests to the MAP;

[0019] When there is repetition in all the URL of the upgrade maintenance request, the request parameters corresponding to the URL are merged with the URL parameters of the current request, and after the merging is completed, the MAP is updated again.

[0020] Further, when the Mapper proxy object set for the entity is acquired, the following is included: in the Spring IOC container, all Mapper proxy object sets for the entity are acquired through a BaseMapper interface type parameter.

[0021] Further, when the Mapper proxy object method set for the corresponding method of the entity is acquired, the following is included: through a reflection mechanism, it is identified that the return result type of the Mapper proxy object in the Mapper proxy object set is MAP or List <map>The method set of the Mapper proxy object.

[0022] Further, by a reflection mechanism, the method in the Mapper proxy object method set is executed to obtain feedback information of a database, and according to the feedback information, an out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set is generated, including:

[0023] By a reflection mechanism, the method in the Mapper proxy object method set is executed, and the field of the entity is identified by a Mybatis interceptor;

[0024] According to the identified field of the entity, the out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set is generated.

[0025] In a second aspect, the application provides a device for generating in and out parameter entities in enterprise software upgrading, including:

[0026] An in-parameter entity generation module is configured to receive an upgrading and maintenance request triggered by all front ends for operating the software to be upgraded, copy the upgrading and maintenance request data to a development environment for analysis, and generate a corresponding in-parameter entity;

[0027] A proxy set acquisition module is configured to analyze the entity in the software to be upgraded and the corresponding method of the entity, acquire a Mapper proxy object set for the entity and a Mapper proxy object method set for the corresponding method of the entity;

[0028] An out-parameter entity generation module is configured to execute the method in the Mapper proxy object method set by a reflection mechanism to obtain feedback information of a database, and generate an out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the feedback information.

[0029] In a third aspect, the application provides a computer device, including a processor, a memory and a computer program; the memory is configured to store the computer program; the processor is configured to execute the computer program stored in the memory to implement the method for generating in and out parameter entities in enterprise software upgrading.

[0030] Compared with the prior art, the application has the following advantages:

[0031] The present invention provides a method for generating input and output parameter entities in enterprise software upgrade and related equipment thereof. The method receives upgrade maintenance requests triggered by all front-end operations on the software to be upgraded, copies the upgrade maintenance request data to a development environment for parsing to generate corresponding input parameter entities, parses the entities in the software to be upgraded and the corresponding methods of the entities, obtains a Mapper proxy object set for the entities and a Mapper proxy object method set for the corresponding methods of the entities, executes the methods in the Mapper proxy object method set through a reflection mechanism to obtain feedback information from a database, and generates output parameter entities corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the feedback information, thereby reducing the upgrade and maintenance costs of enterprise-level software projects and improving the upgrade and maintenance efficiency of enterprise-level software projects. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 This is a flow chart of a method for generating input and output reference entities in enterprise software upgrades according to the present invention;

[0033] Figure 2 This is a structural diagram of a device for generating input and output reference entities in enterprise software upgrades according to the present invention;

[0034] Figure 3 It is a schematic diagram of the architecture of the computer device of the present invention. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0036] It should be noted that, when the terms "first," "second," and the like appear in the specification and claims of the present invention and the accompanying drawings, they are intended to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, such that the embodiments of the present invention described herein can be practiced in orders other than those illustrated or described herein.

[0037] Example 1

[0038] See also Figure 1 and Figure 3 The embodiment provides a generation method of input and output parameter entities in enterprise software upgrading, comprising steps S101, S102 and S103. The method comprises the following steps: receiving all upgrade maintenance requests triggered by front ends for operation of software to be upgraded; copying the upgrade maintenance request data to a development environment for analysis, so as to generate corresponding input parameter entities; analyzing entities in the software to be upgraded and corresponding methods of the entities; obtaining a Mapper proxy object set for the entities and a Mapper proxy object method set for the corresponding methods of the entities; executing the methods in the Mapper proxy object method set through a reflection mechanism, so as to obtain feedback information of a database; and generating output parameter entities corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the feedback information, so as to reduce the upgrade maintenance cost of enterprise software projects and improve the upgrade maintenance efficiency of enterprise software projects.

[0039] It should be noted that in the method for generating in-out parameter entities in enterprise software upgrading, steps S101, S102 and S103 can be run on a computer device, which is the execution subject of all or part of the steps in the method for generating in-out parameter entities in enterprise software upgrading. In addition to performing steps S101, S102 and S103 in this embodiment, the computer device can also run some or all of the steps of the methods described below. The computer device can include a memory, a processor, and a network interface that are connected to each other for communication through a system bus. Among them, those skilled in the art in the technical field can understand that the computer device herein is a device that can automatically perform numerical calculation and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc. The computer device can be a smart phone, a smart wearable device, or other computing device. The computer device can interact with the user through a keyboard, a mouse, a remote control, a touchpad, or a voice control device, etc. The memory includes at least one type of readable storage medium, which includes flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory can be an internal storage unit of the computer device, such as the hard disk or memory of the computer device. In other embodiments, the memory can also be an external storage device of the computer device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device. Of course, the memory can include both the internal storage unit and the external storage device of the computer device.

[0040] Specific to step S101, receive all front-end operation triggers for the software to be upgraded Upgrade maintenance request, copy the upgrade maintenance request data to the development environment for analysis, to generate the corresponding input entity. For example, all front-end pages of the software to be upgraded are clicked to trigger the generation of upgrade maintenance requests, and the local computer device receives the upgrade maintenance requests. In some preferred embodiments, copying the upgrade maintenance request data to the development environment for analysis to generate the corresponding input entity can include: setting a request parameter filter, the request parameter filter is used to capture all the upgrade maintenance requests; save all the upgrade maintenance requests captured by the request parameter filter to the MAP; convert all the upgrade maintenance requests saved in the MAP to a JSON file, and copy the JSON file from the test environment to the local development environment for analysis to generate the corresponding input entity. Further, saving all the upgrade maintenance requests captured by the request parameter filter to the MAP can include: corresponding all the upgrade maintenance request URLs to the MAP key, and corresponding all the upgrade maintenance request request parameters to the MAP value; save the MAP key corresponding to all the upgrade maintenance request URLs to the MAP, and save the MAP value corresponding to all the upgrade maintenance request request parameters to the MAP. Further, saving the MAP key corresponding to all the upgrade maintenance request URLs to the MAP, and saving the MAP value corresponding to all the upgrade maintenance request request parameters to the MAP can include: judging whether all the upgrade maintenance request URLs exist duplication, when there is no duplication, saving the MAP key corresponding to all the upgrade maintenance request URLs to the MAP, and saving the MAP value corresponding to all the upgrade maintenance request request parameters to the MAP; when all the upgrade maintenance request URLs exist duplication, performing a union fusion of the request parameters corresponding to the URLs and the URL parameters of the current request, and after the fusion is completed, updating to the MAP again.

[0041] It should be noted that after the front end initiates a request, the request parameters can be intercepted. For example, a request parameter filter can be set to capture all requests sent by the front end, and the URLs of all requests are used as the keys of the MAP, and the request parameters are used as the values ​​of the MAP and saved in the MAP. In the specific data saving process, it can be determined whether there are duplicate URLs. If there are duplicate URLs, the request parameters corresponding to the URL need to be merged with the URL parameters of this request. After the fusion is completed, it is updated to the MAP again. After the MAP data is saved, the saved MAP can be converted into a JSON file, and the JSON file can be copied from the test environment, and then the JSON file can be parsed in the local development environment to generate the corresponding input parameter entity. For example, developers and testers perform coverage testing in the test environment. After the test is completed, the JSON file containing the request parameters is exported from the test system. Get the JSON file, parse the code in the local development environment, and generate the corresponding input parameter entity according to the relevant logic.

[0042] It should be noted that the request parameter filter filters all requests and stores the request parameters in the parameter result container for subsequent local analysis in the offline development environment. When parsing the JSON file in the local development environment, an offline request parameter parser can be set to parse the JSON parameter file generated by the test, obtain all request URLs by identifying the RestController annotations, match them according to the key values ​​of the JSON parameter file, and translate and generate the corresponding input parameter entity objects. Among them, the parsing of the offline request parameter parser is mainly reflected in the identification of RestController annotations and their methods, and offline JSON parameter document parsing. It should be noted that in Web applications, the request parameter filter can be used to preprocess requests before the request reaches the Servlet, and can be used for identity authentication, logging, etc. In this embodiment, the request parameter filter is used to capture front-end request parameters to prepare for the generation of input parameter entities. JSON file is a lightweight data exchange format that is easy for people to read and write, and also easy for machines to parse and generate. In this embodiment, the request parameters are serialized into JSON format to facilitate subsequent processing and generation of input parameter entities.

[0043] Specific to steps S102 and S103, the entity in the software to be upgraded and the corresponding method of the entity are parsed, a Mapper proxy object set for the entity and a Mapper proxy object method set for the corresponding method of the entity are obtained; through a reflection mechanism, the methods in the Mapper proxy object method set are executed to obtain feedback information of a database, and according to the feedback information, an out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set is generated. Steps S102 and S103 together realize the generation of the out-parameter entity. In some preferred embodiments, when the Mapper proxy object set for the entity is obtained, it can include: in a Spring IOC container, obtaining all Mapper proxy objects for the entity through a BaseMapper interface type parameter. When the Mapper proxy object method set for the corresponding method of the entity is obtained, it can include: through a reflection mechanism, identifying that the Mapper proxy object return result type in the Mapper proxy object set is MAP or List <map>In some preferred embodiments, the method of executing the methods in the method set of the Mapper proxy object set by the reflection mechanism to obtain the feedback information of the database, and generating the out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the feedback information can comprise: executing the methods in the Mapper proxy object method set by the reflection mechanism, and identifying the fields of the entity by the Mybatis interceptor; generating the out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the identified fields of the entity. Wherein, the fields of the entity identified by the Mybatis interceptor are the feedback information of the database. The Spring IOC container refers to the IOC container of the Spring framework, and the IOC container of the Spring framework is responsible for instantiating, configuring and assembling objects. The IOC container of the Spring framework has the feature of reducing the coupling degree between computer codes. The reflection mechanism refers to a feature in the Java language, which allows a running Java program to inspect itself and directly manipulate internal properties. In this embodiment, the reflection mechanism can be used to dynamically identify and execute the methods of the Mapper proxy object. The Mybatis interceptor refers to a persistence layer framework supporting customized SQL, stored procedures and advanced mapping. The Mybatis interceptor allows users to intercept the process of method execution through the interceptor, thereby performing additional processing, such as automatically generating the out-parameter entity.

[0044] It should be noted that in the out-parameter entity generation process, all Mapper proxy objects can be obtained from the Spring IOC container through the BaseMapper type, and the Mapper proxy object methods are traversed through the reflection mechanism, and then the parameter set is constructed, and finally the Mapper proxy object method is executed. In the process of executing the Mapper proxy object method, it will be intercepted by the Mybaits interceptor, and the intercepted method is used to construct the expected result. By obtaining the execution method result, the parameter entity class can be constructed. Specifically, it can include: identifying the method that needs to generate the out-parameter entity, reflecting the execution entity method, intercepting the method execution result, and encapsulating the target result; when identifying the method that needs to generate the out-parameter entity, the developer triggers the analysis program, and the program scans all Mappers and obtains the Mapper proxy method set through the reflection mechanism. When reflecting the execution entity method, the Mapper proxy method is obtained, and the reflection mechanism is used to judge whether the method needs to be converted, and the parameter type required by the method is identified, thereby constructing the parameters required for the execution of the Mapper proxy method. After the parameters are constructed, the Mapper proxy method can be finally executed. When intercepting the method execution result and encapsulating the target result, in the process of executing the Mapper proxy object method, the method execution result will be intercepted by the Mybaits interceptor, and the interceptor obtains the method execution result, translates it into a Java object attribute type according to the field type, and synchronizes the field name into a Java camel style type. It should be noted that in order to realize the generation of the out-parameter entity, the out-parameter parser can be set. The out-parameter parser first analyzes the Mapper proxy object set in the program. The corresponding virtual parameters are constructed, and after the construction is completed, the Mapper proxy object method is executed through the reflection mechanism. It mainly includes identifying the method that needs to generate the out-parameter entity, reflecting the execution entity method, intercepting the method execution result and encapsulating the target result, and constructing the out-parameter entity according to the execution result. Among them, when identifying the method that needs to generate the out-parameter entity, all BaseMappers can be obtained through the Spring IOC container, and the method set that needs to be executed by the Mapper proxy object is obtained through the reflection mechanism. When reflecting the execution entity method, the Mapper proxy object method is obtained, and the parameter type required by the method is identified, thereby constructing the parameters required for the execution of the Mapper proxy object method. After the parameters are constructed, the Mapper proxy object method can be finally executed. When intercepting the method execution result and encapsulating the target result, the method execution result is mapped to return the result set according to the field type and field name. In Mybatis, the Mapper interface does not need to be implemented by the user, and the framework will automatically create a proxy object to execute the SQL operation. In this embodiment, the Mapper method that needs to generate the out-parameter entity is identified through the reflection mechanism. In addition, the input parameter entity and the output parameter entity respectively refer to the parameter object (input parameter) received by the method or function and the result object (output parameter) returned after the method is executed.In this embodiment, these entities are generated by automated means to simplify the transmission and processing of parameters. In a project using MyBatis integrated with the Spring framework, BaseMapper refers to a basic Mapper interface that defines a series of general data access methods.

[0045] Embodiment Two

[0046] Referring to Figure 1 、 2 The embodiment provides an in-parameter entity generation device in enterprise software upgrading, which comprises:

[0047] The in-parameter entity generation module is configured to receive upgrade maintenance requests sent by all front ends after operation on the software to be upgraded, copy the upgrade maintenance request data to a development environment for analysis, and generate corresponding in-parameter entities.

[0048] The proxy set acquisition module is configured to analyze entities in the software to be upgraded and corresponding methods of the entities, acquire a set of Mapper proxy objects for the entities and a set of Mapper proxy object methods for the corresponding methods of the entities.

[0049] The out-parameter entity generation module is configured to execute methods in the set of Mapper proxy object methods through a reflection mechanism to obtain feedback information of a database, and generate out-parameter entities corresponding to the set of Mapper proxy objects and the set of Mapper proxy object methods according to the feedback information.

[0050] In this embodiment, by receiving upgrade maintenance requests sent by all front ends after operation on the software to be upgraded, copying the upgrade maintenance request data to a development environment for analysis, and generating corresponding in-parameter entities, analyzing entities in the software to be upgraded and corresponding methods of the entities, acquiring a set of Mapper proxy objects for the entities and a set of Mapper proxy object methods for the corresponding methods of the entities, executing methods in the set of Mapper proxy object methods through a reflection mechanism to obtain feedback information of a database, and generating out-parameter entities corresponding to the set of Mapper proxy objects and the set of Mapper proxy object methods according to the feedback information, the upgrading and maintenance cost of enterprise-level software projects is reduced, and the upgrading and maintenance efficiency of enterprise-level software projects is improved.

[0051] Embodiment Three

[0052] Referring to Figure 1 、 3 The embodiment provides a computer device, comprising a processor, a memory and a computer program; the memory is used for storing the computer program; the processor is used for executing the computer program stored in the memory, so as to realize the generation method of the in-parameter entity in the enterprise software upgrade, the generation method comprises the following steps: receiving all upgrade maintenance requests sent by front ends after the front ends operate the software to be upgraded; copying the upgrade maintenance request data to a development environment for analysis, so as to generate corresponding in-parameter entities; analyzing entities in the software to be upgraded and corresponding methods of the entities; obtaining a Mapper proxy object set for the entities and a Mapper proxy object method set for the corresponding methods of the entities; executing the methods in the Mapper proxy object method set through a reflection mechanism, so as to obtain feedback information of a database; and generating out-parameter entities corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the feedback information, so as to reduce the upgrade maintenance cost of the enterprise software project and improve the upgrade maintenance efficiency of the enterprise software project.

[0053] It should be noted that the related device of the generation method of the in-parameter entity in the enterprise software upgrade includes but is not limited to the generation device of the in-parameter entity in the enterprise software upgrade, the computer device and the like in the above embodiment.

[0054] It should be noted that the above embodiment is only a preferred specific implementation of the present application, the protection scope of the present application is not limited to this, any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, all the changes or replacements should be covered in the protection scope of the present application, and the protection scope of the present application should be subject to the protection scope of the claims.< / map> < / map>

Claims

1. A method for generating in-out parameter entities in enterprise software upgrade, characterized in that, The method comprises the following steps: Receiving all front-end operation triggers of the software to be upgraded to generate upgrade maintenance requests, copying the upgrade maintenance request data to the development environment for analysis to generate corresponding input entities; Analyzing the entities in the software to be upgraded and the corresponding methods of the entities, obtaining a set of Mapper proxy objects for the entities and a set of Mapper proxy object methods for the corresponding methods of the entities; Through the reflection mechanism, the methods in the set of Mapper proxy object methods are executed to obtain feedback information of the database, and the feedback information is used to generate output entities corresponding to the set of Mapper proxy objects and the set of Mapper proxy object methods.

2. The method for generating input and output parameter entities in enterprise software upgrade according to claim 1, characterized in that: Receiving all front-end operation triggers of the software to be upgraded to generate upgrade maintenance requests, including: receiving all upgrade maintenance requests sent after the front-end clicks on the pages of the software to be upgraded.

3. The method for generating input and output parameter entities in enterprise software upgrade according to claim 1, characterized in that: Copy the upgrade maintenance request data to the development environment for analysis to generate corresponding input entities, including: Setting a request parameter filter, the request parameter filter is used to capture all the upgrade maintenance requests; Saving all the upgrade maintenance requests captured by the request parameter filter to the MAP; Convert all the upgrade maintenance requests saved in the MAP to JSON files, and copy the JSON files from the test environment to the local development environment for analysis to generate corresponding input entities.

4. The method of claim 3, wherein the method further comprises: generating an input parameter entity for the enterprise software upgrade. Saving all the upgrade maintenance requests captured by the request parameter filter to the MAP, including: Corresponding all the request parameters of the upgrade maintenance requests to the values of the MAP, and corresponding the request parameters of all the upgrade maintenance requests to the values of the MAP. Corresponding the request parameters of all the upgrade maintenance requests to the values of the MAP, and corresponding the request parameters of all the upgrade maintenance requests to the values of the MAP.

5. The method of claim 4, wherein the method further comprises: Corresponding the request parameters of all the upgrade maintenance requests to the values of the MAP, and corresponding the request parameters of all the upgrade maintenance requests to the values of the MAP, including: Determine whether the URLs of all the upgrade maintenance requests are repeated, if not, save the keys of the MAP corresponding to the URLs of all the upgrade maintenance requests to the MAP, and save the values of the MAP corresponding to the request parameters of all the upgrade maintenance requests to the MAP; When all the URLs of the upgrade maintenance requests are repeated, the request parameters corresponding to the URLs are merged with the URL parameters of the current request, and after the fusion is completed, it is updated to the MAP again.

6. The method for generating input and output parameter entities in enterprise software upgrade according to claim 1, characterized in that: When obtaining the set of Mapper proxy objects for the entities, in the Spring IOC container, all the set of Mapper proxy objects for the entities are obtained through the BaseMapper interface type parameter.

7. The method for generating input and output parameter entities in enterprise software upgrade according to claim 1, characterized in that: When acquiring the Mapper proxy object method set of the corresponding method of the entity, the method comprises: identifying, through a reflection mechanism, that the Mapper proxy object return result type in the Mapper proxy object set is MAP or List <map>The method set.< / map> 8. The method of claim 1-7, wherein, The method in the Mapper proxy object method set is executed through a reflection mechanism to obtain feedback information of a database, and an out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set is generated according to the feedback information, including: The method in the Mapper proxy object method set is executed through a reflection mechanism, and the fields of the entity are identified through a Mybatis interceptor; According to the identified fields of the entity, an out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set is generated.

9. An apparatus for generating in-out parameter entities in enterprise software upgrade, characterized in that, Including: The input parameter entity generation module is configured to receive upgrade maintenance requests triggered by all front ends for operating the software to be upgraded, copy the upgrade maintenance request data to a development environment for analysis, and generate corresponding input parameter entities; The proxy set acquisition module is configured to analyze the entity in the software to be upgraded and the corresponding method of the entity, acquire a Mapper proxy object set for the entity and a Mapper proxy object method set for the corresponding method of the entity; The out-parameter entity generation module is configured to execute the method in the Mapper proxy object method set through a reflection mechanism to obtain feedback information of a database, and generate an out-parameter entity corresponding to the Mapper proxy object set and the Mapper proxy object method set according to the feedback information.

10. A computer device, comprising: Including: A processor, a memory and a computer program; the memory is configured to store the computer program; The processor is configured to execute the computer program stored in the memory to implement the method for generating input and output parameter entities in enterprise software upgrading according to any one of claims 1-8.

Images