Data processing method and device, storage medium and program product

Abstract

The embodiment of the invention provides a data processing method and device, a storage medium and a program product, in the method, a first application construction tool constructs a target application component through a target meta-model of a first version deployed on the first application construction tool, and generates corresponding first modeling data. And if it is determined that the target meta-model has a second version lower than the first version, generating second modeling data compatible with the target meta-model of the second version according to meta-model change information between the target meta-model of the first version and the target meta-model of the second version. Therefore, the first application modeling tool has the first modeling data and the second modeling data which are compatible with the target meta-models of different versions, even if the versions of the second application building tool and the first application building tool are not consistent, the first application building tool is not consistent with the second application building tool. And the target modeling data compatible with the target meta-model of the target version deployed by the second application construction tool can also be provided for the second application construction tool, so that the second application construction tool constructs the target application component based on the target modeling data.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, device, storage medium and program product. Background Art

[0002] In the field of software development, application developers can use application building tools to build various applications. In some application building tools, in order to help application developers quickly design and build applications, a variety of meta models corresponding to different application building functions are provided. Application developers can configure these meta models to achieve modeling of different application components. Furthermore, based on the modeling data corresponding to each application component, the code corresponding to the application can be generated, thereby realizing the development of the application.

[0003] In actual applications, application developers can also use application building tools to distribute the modeling data they build during the application development process to other application developers. In this way, other application developers can reuse these modeling data without having to build a certain application component from scratch, which can effectively improve the development efficiency of the application.

[0004] However, in actual applications, different application developers may use different versions of an application construction tool. Correspondingly, the metamodels in different versions of the application construction tool are also different. When reusing modeling data, the modeling data may not be reused due to incompatibility between the modeling data and the metamodel in the application construction tool. Summary of the invention

[0005] Embodiments of the present application provide a data processing method, device, storage medium, and program product to solve compatibility issues when modeling data is reused on application building tools of different versions.

[0006] In a first aspect, an embodiment of the present application provides a data processing method, which is applied to a first application construction tool, wherein a metamodel set for constructing different application components is deployed in the first application construction tool, and the method includes: In response to a construction operation of a target application component through a first version of a target metamodel, obtaining generated first modeling data, wherein the metamodel set includes the first version of the target metamodel; Determining a second version of the target metamodel according to pre-stored metamodel version information, where the second version is lower than the first version; generating second modeling data corresponding to the first modeling data according to metamodel change information between the first version of the target metamodel and the second version of the target metamodel, wherein the second modeling data is compatible with the second version of the target metamodel; In response to a modeling data request corresponding to the target application component sent by a second application construction tool, target modeling data is sent to the second application construction tool so that the second application construction tool builds the target application component based on the target modeling data, the target modeling data is compatible with a target version corresponding to a target metamodel deployed in the second application construction tool, and the first modeling data and the second modeling data include the target modeling data.

[0007] In a second aspect, an embodiment of the present application provides a data processing device, which is applied to a first application construction tool, wherein a set of metamodels for constructing different application components is deployed in the first application construction tool, and the device includes: A first acquisition module, configured to acquire generated first modeling data in response to a construction operation of a target application component using a first version of a target metamodel, wherein the metamodel set includes the first version of the target metamodel; A first processing module is configured to determine a second version of the target metamodel according to pre-stored metamodel version information, the second version being lower than the first version; generate second modeling data corresponding to the first modeling data according to metamodel change information between the target metamodel of the first version and the target metamodel of the second version, the second modeling data being compatible with the target metamodel of the second version; and generate a target data packet corresponding to the target application component, the target data packet including the first modeling data and the second modeling data; A first sending module is used to respond to a modeling data request corresponding to the target application component sent by a second application construction tool, and send target modeling data to the second application construction tool, so that the second application construction tool builds the target application component based on the target modeling data, the target modeling data is compatible with a target version corresponding to a target metamodel deployed in the second application construction tool, and the first modeling data and the second modeling data include the target modeling data.

[0008] In a third aspect, an embodiment of the present application provides a data processing method, which is applied to a second application construction tool, wherein a set of metamodels for constructing different application components is deployed in the second application construction tool, and the method includes: Sending a modeling data request corresponding to a target application component to a first application construction tool, wherein the target application component is constructed by the first application construction tool using a first version of a target metamodel; receiving target modeling data sent by the first application modeling tool, the target modeling data being compatible with a target version corresponding to the target metamodel included in the metamodel set, the target modeling data being included in first modeling data and second modeling data, the first modeling data being modeling data acquired by the first application building tool in response to a building operation on the target application component, the second modeling data being generated based on the first modeling data, the second modeling data being compatible with a second version of the target metamodel, the second version being lower than the first version; The target application component is constructed according to the target modeling data.

[0009] In a fourth aspect, an embodiment of the present application provides a data processing device, which is applied to a second application construction tool, wherein a set of metamodels for constructing different application components is deployed in the second application construction tool, and the device includes: A second sending module, configured to send a modeling data request corresponding to a target application component to the first application building tool, wherein the target application component is built by the first application building tool using a first version of a target metamodel; a second acquisition module, configured to receive target modeling data sent by the first application modeling tool, the target modeling data being compatible with a target version corresponding to the target metamodel contained in the metamodel set, the target modeling data being included in first modeling data and second modeling data, the first modeling data being modeling data acquired by the first application building tool in response to a building operation on the target application component, the second modeling data being generated based on the first modeling data, the second modeling data being compatible with a second version of the target metamodel, the second version being lower than the first version; The second processing module is used to construct the target application component according to the target modeling data.

[0010] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a communication interface; wherein a computer program is stored on the memory, and when the computer program is executed by the processor, the processor can at least implement the data processing method described in the first aspect or the third aspect.

[0011] In the sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor of an electronic device, the processor can at least implement the data processing method described in the first aspect or the third aspect.

[0012] In the seventh aspect, an embodiment of the present application provides a computer program product, including: a computer program or instructions, when the computer program or instructions are executed by a processor of an electronic device, the processor can at least implement the data processing method as described in the first aspect or the third aspect.

[0013] The data processing method provided in the embodiment of the present application is used to realize the reuse of modeling data corresponding to application components by application construction tools of different versions, and solve the problem that modeling data corresponding to application components are incompatible in application construction tools of different versions. For the convenience of description, the application construction tool used to generate the modeling data of the target application component is called the first application construction tool, and the application construction tool used to reuse the modeling data of the target application component is called the second application construction tool. In order to ensure that the second application construction tool can reuse the modeling data corresponding to the target application component, first, the first application construction tool responds to the construction operation of the target application component through the first version of the target metamodel, and obtains the generated first modeling data. Among them, the first version of the target metamodel is included in the metamodel set deployed in the first application construction tool for building different application components. Then, according to the pre-stored metamodel version information, it is determined whether the target metamodel has a second version lower than the first version; if there is a second version, according to the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, the second modeling data corresponding to the first modeling data is generated, wherein the second modeling data is compatible with the target metamodel of the second version. Since the first application construction tool further generates second modeling data corresponding to target metamodels of other versions lower than the currently used version (i.e., target metamodels of the second version) after generating first modeling data corresponding to the currently used version, the first application construction tool has multiple modeling data compatible with target metamodels of different versions. Afterwards, in response to a modeling data request corresponding to a target application component sent by the second application construction tool, even if the version of the second application construction tool is inconsistent with that of the first application construction tool, i.e., the version of the target metamodel deployed in the second application construction tool is not the first version, the first application construction tool can provide the second application construction tool with target modeling data compatible with the version of the target metamodel deployed in the second application construction tool, and send the target modeling data to the second application construction tool, so that the second application construction tool reuses the acquired target modeling data, i.e., builds the target application component based on the acquired target modeling data. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0015] Figure 1 A schematic diagram of a deployment environment of an application building tool provided in an embodiment of the present application; Figure 2 An interactive flow chart of a data processing method provided in an embodiment of the present application; Figure 3 A flowchart of a second modeling data generating method provided in an embodiment of the present application; Figure 4 An interactive flow chart of another data processing method provided in an embodiment of the present application; Figure 5 An interactive flow chart of a target application component recommendation method provided in an embodiment of the present application; Figure 6 An interactive flow chart of a method for acquiring a target data packet provided in an embodiment of the present application; Figure 7 It is a flowchart of the data processing method provided in the embodiment of the present application when it is executed on the first application building tool side; Figure 8 It is a flowchart of the data processing method provided in the embodiment of the present application when it is executed on the second application construction tool side; Fig. 9 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application; Fig.10 A schematic diagram of the structure of another data processing device provided in an embodiment of the present application; Fig.11 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0016] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0017] It should be noted that, in the case of user information involved in the embodiments of this application, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation portals for users to choose to authorize or refuse. In addition, the various models involved in this application (including but not limited to language models or large models) are in compliance with relevant laws and standards.

[0018] In addition, the step sequence in the following method embodiments is only an example and not a strict limitation.

[0019] Before introducing the data processing method provided in the embodiments of the present application, the terms or concepts involved in the embodiments of the present application are first explained.

[0020] Application components refer to the basic functional units or modules that make up an application. In the field of software development, generally, each application component is responsible for implementing specific functions or services, and different application components can be independently developed, tested, and deployed.

[0021] Meta Model refers to a template with predefined functions, which is used to provide a standardized way for application developers to describe and configure application components, so that developers can build applications through simple configuration rather than complex programming.

[0022] Application building tools refer to software tools or platforms that help application developers quickly design and build applications. Application building tools can be deployed with a set of metamodels for building different application components. Different metamodels in the metamodel set can provide different application building functions, so that application developers can configure these metamodels to achieve modeling of different application components. Furthermore, based on the modeling data corresponding to each application component, the code corresponding to the application can be generated, thereby achieving application development.

[0023] The same application construction tool may have multiple different versions, and the versions of the same meta-model included in different versions of the application construction tool may be the same or different.

[0024] In application development scenarios, in order to improve application development efficiency, the modeling data generated by building a certain application component through the metamodel in the application building tool can often be reused. For example, when developing application A, the application developer developed the "User Center" application component. When developing application B, if the "User Center" is also needed, the developer can choose to reuse the modeling data corresponding to the previously developed "User Center" application component to implement the construction of the "User Center" in application B, without having to build the "User Center" from scratch.

[0025] In the embodiment of the present application, for the convenience of description, the application construction tool used to generate the modeling data of the target application component is referred to as the first application construction tool, and the application construction tool used to reuse the modeling data of the target application component is referred to as the second application construction tool. The first application construction tool and the second application construction tool are the same or different versions of the same application construction tool.

[0026] Assume that the first application construction tool generates corresponding modeling data x when constructing the target application component through the metamodel deployed thereon. It is easy to understand that in the scenario where the modeling data x corresponding to the target application component is reused, if the version of the first application construction tool is consistent with the version of the second application construction tool, then the second application construction tool and the first application construction tool have the same version of the metamodel deployed, and the modeling data x must be able to pass various data verifications in the second application construction tool, that is, compatible with the metamodel deployed in the second application construction tool, so that the modeling data x can be reused by the second application construction tool to construct the target application component.

[0027] If the version of the first application building tool is inconsistent with the version of the second application building tool, there may be two situations: In the first case, the versions of the metamodel used to construct the target application component in the first application construction tool and the second application construction tool are consistent, and the modeling data x is compatible with the metamodel deployed in the second application construction tool for constructing the target application component, and then the modeling data x can be reused by the second application construction tool to construct the target application component.

[0028] In the second situation, the versions of the metamodel used to construct the target application component in the first application construction tool and the second application construction tool are inconsistent, the modeling data x is incompatible with the metamodel in the second application construction tool, the modeling data x cannot be reused, and the target application component cannot be constructed based on the modeling data x.

[0029] In view of the problem that the modeling data x in the second situation is incompatible with the metamodel in the second application construction tool and the modeling data x cannot be reused, in the related art, the modeling data x can be reused by upgrading the version of the first application construction tool or the second application construction tool to make the two versions consistent. However, in actual applications, users of different versions of application construction tools often have their specific usage requirements, and the version upgrade of the application construction tool may have a certain impact on its normal use; in addition, it is also time-consuming and laborious to update the application construction tools of all application construction tool users to the same version.

[0030] Based on this, an embodiment of the present application provides a data processing method, through which the compatibility problem of modeling data when reused on different versions of application construction tools can be solved without upgrading the version of the application construction tool. The basic idea is: after the first application construction tool constructs the target application component through the first version of the target metamodel deployed thereon and generates the corresponding first modeling data, if it is determined that the target metamodel has a second version lower than the first version, then according to the metamodel change information between the first version of the target metamodel and the second version of the target metamodel, the second modeling data corresponding to the first modeling data is generated, wherein the second modeling data is compatible with the second version of the target metamodel. Since the first application construction tool has multiple modeling data compatible with different versions of target metamodels, in response to the modeling data request corresponding to the target application component sent by the second application construction tool, even if the version of the second application construction tool is inconsistent with the version of the first application construction tool, and the version of the target metamodel deployed in the second application construction tool is not the first version (for example, the second version), the first application construction tool can also provide the second application construction tool with target modeling data compatible with the version of the target metamodel deployed in the second application construction tool, and send the target modeling data to the second application construction tool, so that the second application construction tool reuses the acquired target modeling data, that is, builds the target application component based on the acquired target modeling data.

[0031] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0032] Before introducing the data processing method provided in the embodiment of the present application, the deployment environment of the first application construction tool and the second application construction tool involved in the embodiment of the present application is first described.

[0033] In actual applications, application building tools can be deployed in the public area of ​​a public cloud for use by different users. When different users use application building tools deployed in the public area of ​​a public cloud, the application building tools may be used as both the producer and the reuser of modeling data corresponding to the target application component. However, in this scenario, since there is only one version of the application building tool, there will be no compatibility issues when the modeling data is reused on different versions of the application building tool.

[0034] Based on this, the first application construction tool and the second application construction tool involved in the embodiment of the present application are two independently deployed application construction tools, and their deployment scenarios include but are not limited to: Figure 1 The situation indicated.

[0035] Figure 1 A schematic diagram of a deployment environment of an application construction tool provided in an embodiment of the present application. Figure 1 As shown, in the first case, the first application construction tool and the second application construction tool are respectively deployed in different virtual private clouds (Virtual Private Cloud, VPC) in the public cloud. Specifically, they can be different VPCs in the public cloud of the same region, or different VPCs in public clouds of different regions. In the second case, the first application construction tool and the second application construction tool are respectively deployed in different private clouds. In the third case, one of the first application construction tool and the second application construction tool is deployed in a VPC in the public cloud, and the other is deployed in a private cloud, for example: the first application construction tool is deployed in a VPC in the public cloud, and the second application construction tool is deployed in a private cloud; or, the first application construction tool is deployed in a private cloud, and the second application construction tool is deployed in a VPC in the public cloud.

[0036] Optionally, Figure 1 In the three scenarios shown in the figure, the communication connections between different VPCs, between different private clouds, and between a VPC and a private cloud can be connected or disconnected.

[0037] In actual applications, compatibility issues when modeling data is reused on application construction tools of different versions may be caused by the version of the first application construction tool being higher than the version of the second application construction tool, or may be caused by the version of the first application construction tool being lower than the version of the second application construction tool. Since there is a certain mapping relationship between the version of the application construction tool and the version of the metamodel deployed in the application construction tool, further, compatibility issues when modeling data is reused on application construction tools of different versions can also be understood as being caused by the version of the metamodel in the first application construction tool being higher than the version of the metamodel in the second application construction tool, or being caused by the version of the metamodel in the first application construction tool being lower than the version of the metamodel in the second application construction tool.

[0038] In view of the above two compatibility issues during modeling data reuse caused by inconsistent application construction tool versions or inconsistent metamodel versions, two different solutions are provided, which are respectively described below in conjunction with specific embodiments.

[0039] The following first describes the corresponding data processing method when the version of the metamodel in the first application construction tool is higher than the version of the metamodel in the second application construction tool.

[0040] Figure 2 An interactive flow chart of a data processing method provided in an embodiment of the present application, such as Figure 2 As shown, the following steps may be included: 201. In response to a construction operation of a target application component using a first version of a target metamodel, a first application construction tool obtains generated first modeling data.

[0041] 202. The first application construction tool determines a second version of the target metamodel based on pre-stored metamodel version information, where the second version is lower than the first version; and generates second modeling data corresponding to the first modeling data based on metamodel change information between the target metamodel of the first version and the target metamodel of the second version, where the second modeling data is compatible with the target metamodel of the second version.

[0042] 203. The second application construction tool sends a modeling data request corresponding to the target application component to the first application construction tool.

[0043] 204. The first application construction tool sends target modeling data to the second application construction tool in response to a modeling data request corresponding to a target application component. The target modeling data is compatible with a target version corresponding to a target metamodel deployed in the second application construction tool. The first modeling data and the second modeling data include the target modeling data.

[0044] 205. The second application construction tool constructs a target application component according to the target modeling data.

[0045] In the embodiment of the present application, the target application component is an application component that needs to be constructed by reusing modeling data. Both the first application construction tool and the second application construction tool are deployed with a set of metamodels for constructing different application components. For ease of understanding, an exemplary explanation is given by taking the metamodel used to construct the target application component as the target metamodel in the metamodel set as an example. Optionally, the number of metamodels corresponding to the target metamodel can be one or more, and the type of metamodel corresponding to the target metamodel can also be one or more.

[0046] For the sake of distinction, the target metamodel in the metamodel set of the first application construction tool is referred to as the target metamodel of the first version; the target metamodel in the metamodel set of the second application construction tool is referred to as the target metamodel of the target version. In the scenario illustrated in the embodiment of the present application, it is assumed that the first version is higher than the target version.

[0047] In summary, in the data processing method provided in the embodiment of the present application, the first application construction tool, as the producer of the modeling data of the target application component, not only generates the first modeling data corresponding to the first version of the target metamodel currently in use, but also further generates the second modeling data corresponding to the second version of the target metamodel lower than the first version. In other words, in the modeling data generation stage of the target application component, the first application construction tool generates a plurality of modeling data that are respectively compatible with the first version and the following versions of the target metamodel. Thus, in the case where the target version corresponding to the target metamodel deployed in the second application construction tool is lower than the first version, the second application construction tool can obtain the target modeling data that is compatible with the target metamodel of the target version from the target data packet generated by the first application construction tool and containing a plurality of modeling data, and then construct the target application component based on the target modeling data, thereby realizing the reuse of the modeling data of the target application component.

[0048] To elaborate, first, the first application construction tool obtains the generated first modeling data in response to the construction operation of the target application component through the first version of the target metamodel.

[0049] The first modeling data is the configuration data generated by the user of the first application building tool to instantiate and configure the first version of the target metamodel. Optionally, the first modeling data can be the design data of the target application component, such as: which task processing flow the target application component is to be used to execute, which roles will be involved, what actions different roles will perform in different task processing flows, etc.; the first modeling data can also be the technical implementation data of the target application component, such as: what application programming interface (Application Programming Interface, referred to as API) the target application component will call when executing the task processing flow, and how to call the API, etc.

[0050] Among them, the corresponding data type of the first modeling data depends on the type of the target metamodel of the first version, for example: when the target metamodel of the first version is a metamodel related to the design of the application component, the first modeling data is the design data of the target application component; when the target metamodel of the first version is a metamodel related to the technical implementation of the application component, the first modeling data is the technical implementation data of the target application component. Optionally, the first modeling data may include only one of the design data and the technical implementation data of the target application component, or both. In the embodiment of the present application, the data type of the first modeling data is not limited.

[0051] In an embodiment of the present application, metamodel version information and metamodel change information are pre-stored in the first application construction tool. The metamodel version information is used to record the current version information and historical version information corresponding to each metamodel in the metamodel set deployed in the first application construction tool. The metamodel change information is used to record the change information between different versions of each metamodel in the metamodel set deployed in the first application construction tool, such as: the addition, deletion or modification of fields, etc.

[0052] Based on this, after obtaining the generated first modeling data, the first application construction tool can determine whether the target metamodel has other versions (called the second version) lower than the first version according to the pre-stored metamodel version information. The number of versions corresponding to the second version can be one or more. For example, assuming that there are three versions of the target metamodel, in descending order: V3.0, V2.0 and V1.0, if the first version is V3.0, then the second version includes V2.0 and V1.0.

[0053] If there is a second version lower than the first version, second modeling data corresponding to the first modeling data is generated according to metamodel change information between the target metamodel of the first version and the target metamodel of the second version.

[0054] In actual applications, there are differences in the field information available for instantiation configuration provided by different versions of the target metamodel. Such differences are recorded through metamodel change information. For example, the metamodel change information between two versions of the target metamodel is the addition / deletion / modification of a field information available for instantiation configuration. The modeling data is the configuration data generated by the instantiation configuration of the target metamodel. In other words, there is a correspondence between the fields contained in the modeling data and the field information available for instantiation configuration provided by the target metamodel. Therefore, based on the metamodel change information between the first version of the target metamodel and the second version of the target metamodel, the target field to be changed corresponding to the first modeling data can be determined, and the field information of the target field can be changed to obtain the second modeling data, wherein the second modeling data matches the field information available for instantiation configuration provided by the second version of the target metamodel.

[0055] It is worth noting that both the first modeling data and the second modeling data are modeling data corresponding to the target application component. The difference is that the first modeling data is compatible with the first version of the target metamodel, and the second modeling data is compatible with the second version of the target metamodel.

[0056] If there is no second version lower than the first version, it indicates that when the first application construction tool is released, there is only one version of the target metamodel, namely the first version. At this time, there is no need to perform the above-mentioned second modeling data generation operation.

[0057] Afterwards, when the second application construction tool wants to reuse the modeling data of the target application component, the second application construction tool sends a modeling data request corresponding to the target application component to the first application construction tool. In response to the modeling data request corresponding to the target application component, the first application construction tool sends the target modeling data to the second application construction tool. The target modeling data is compatible with the target version corresponding to the target metamodel deployed in the second application construction tool, and the first modeling data and the second modeling data include the target modeling data.

[0058] In actual applications, in order to facilitate multiple modeling data corresponding to the target application component and compatible with different versions of the target metamodel, optionally, after the first application construction tool generates the second modeling data corresponding to the first modeling data, it can further generate a target data packet corresponding to the target application component, wherein the target data packet contains the first modeling data and the second modeling data.

[0059] In response to a modeling data request corresponding to a target application component sent by the second application construction tool, optionally, the first application construction tool may directly send a target data packet to the second application construction tool so that the second application construction tool obtains target modeling data compatible with the target metamodel of the target version deployed by itself from the target data packet; or, the first application construction tool first obtains target modeling data compatible with the target metamodel of the target version deployed in the second application construction tool from the target data packet, and then sends the target modeling data to the second application construction tool.

[0060] Optionally, the first application construction tool can customize the way to send the target modeling data to the second application construction tool. For example, when the network quality between the first application construction tool and the second application construction tool is good, the target data packet is sent to the second application construction tool; when the network quality between the first application construction tool and the second application construction tool is poor, the target modeling data is filtered out from the target data packet, and then only the target modeling data is sent to the second application construction tool. Thus, the timeliness of the second application construction tool obtaining the target modeling data is effectively guaranteed.

[0061] Finally, the second application construction tool constructs the target application component according to the target modeling data.

[0062] It is understandable that when the target metamodel has a second version lower than the first version, the first application construction tool has modeling metadata compatible with the first and second versions of the target metamodel, respectively. Therefore, no matter which version the target version is lower than the first version, the second application construction tool can obtain target modeling data compatible with the target metamodel of the target version from the first application construction tool.

[0063] In the above embodiment, it is assumed that when the target version is lower than the first version, the process of acquiring the target modeling data that is compatible with the target metamodel of the target version is described. It is easy to understand that in actual applications, when the target version is the first version, the first modeling data can also be acquired from the first application construction tool. Therefore, the data processing method provided in the embodiment of the present application is also applicable to the situation where the target version is the same as the first version, that is, it is applicable to the situation where the same version of the target metamodel is deployed in the first application construction tool and the second application construction tool.

[0064] To facilitate understanding, let's take an example to illustrate. It is assumed that the first version corresponding to the target metamodel deployed in the first application construction tool is V3.0, and the first application construction tool pre-stores metamodel version information indicating that the target metamodel has three versions, V3.0, VV2.0 and V1.0, of which V3.0 is the highest version and V1.0 is the lowest version; the target version corresponding to the target metamodel deployed in the second application construction tool is V3.0.

[0065] Based on the above assumptions, the first application construction tool responds to the construction operation of the target application component through the target metamodel of V3.0, obtains the generated first modeling data (called {modeling data, V3.0}), and then determines that there are versions of the target metamodel lower than V3.0 - V2.0 and V1.0 according to the pre-stored metamodel version information.

[0066] Furthermore, based on the pre-stored metamodel change information and {modeling data, V3.0}, {modeling data, V2.0} compatible with the target metamodel of V2.0 and {modeling data, V1.0} compatible with the target metamodel of V1.0 are generated respectively.

[0067] In the specific implementation process, optionally, {modeling data, V3.0} can be changed according to the metamodel change information between the target metamodel of V3.0 and the target metamodel of V2.0 to generate {modeling data, V2.0}; {modeling data, V3.0} can be changed according to the metamodel change information between the target metamodel of V3.0 and the target metamodel of V1.0 to generate {modeling data, V1.0}. Alternatively, after {modeling data, V2.0} is generated, {modeling data, V2.0} can be changed according to the metamodel change information between the target metamodel of V2.0 and the target metamodel of V1.0 to generate {modeling data, V1.0}.

[0068] Afterwards, when the second application construction tool wants to reuse the modeling data of the target application component, the second application construction tool sends a modeling data request corresponding to the target application component to the first application construction tool. In response to the modeling data request corresponding to the target application component, the first application construction tool sends {modeling data, V3.0} as the target modeling data to the second application construction tool.

[0069] Similarly, if the target version is V2.0, the target modeling data is {modeling data, V2.0}, and if the target version is V1.0, the target modeling data is {modeling data, V1.0}.

[0070] After receiving {modeling data, V3.0}, the second application construction tool constructs the target application component based on {modeling data, V3.0}.

[0071] In summary, the data processing method provided by the embodiment of the present application generates the first modeling data corresponding to the first version of the target metamodel currently in use by the first application construction tool, and generates the second modeling data corresponding to the second version of the target metamodel lower than the first version, so that the first application construction tool has multiple modeling data that are respectively compatible with the first version and the target metamodels below it. Therefore, when the target version corresponding to the target metamodel deployed in the second application construction tool is not higher than the first version, the second application construction tool can obtain the target modeling data compatible with the target metamodel of the target version from the first application construction tool, and then construct the target application component based on the target modeling data, so as to realize the reuse of the modeling data of the target application component.

[0072] The above is an overall description of the data processing method provided in the embodiment of the present application. Next, the process of generating second modeling data compatible with a lower version of the target metamodel based on the metamodel change information between different versions of the target metamodel is described in detail.

[0073] Figure 3 A flowchart of a second modeling data generation method provided in an embodiment of the present application, such as Figure 3 As shown, the following steps may be included: 301. Determine, according to metamodel change information between a target metamodel of a first version and a target metamodel of a second version, a metamodel change category corresponding to a change from a target metamodel of the second version to a target metamodel of the first version.

[0074] Among them, the metamodel change category corresponding to the change from the second version of the target metamodel to the first version of the target metamodel is also the metamodel change category corresponding to the upgrade from the lower version of the target metamodel to the higher version of the target metamodel. It is easy to understand that, when it is known how the lower version of the target metamodel changes to the higher version of the target metamodel, it is also possible to naturally obtain how the higher version of the target metamodel changes to the lower version of the target metamodel, and then obtain the modeling data compatible with the lower version of the target metamodel based on the modeling data compatible with the higher version of the target metamodel.

[0075] Optionally, the metamodel change category includes at least one of the following: change of the type of the target field, change of the type value of the target field, addition of the target field, and deletion of the target field. The type of the field is the data type of the field, such as integer, decimal, character, enumeration, etc. The type value of the field is the specific data value that conforms to the type definition of the field, such as the predefined enumeration value corresponding to the enumeration, etc.

[0076] Regarding the metamodel change category, for example, assuming that there is an "age" field in the target metamodel of the second version, and its corresponding type is an integer, and the type of the "age" field in the target metamodel of the first version is a decimal, then it is determined that the metamodel change category corresponding to the change from the target metamodel of the second version to the target metamodel of the first version includes a type change of the target field, specifically involving a type change of the "age" field.

[0077] For another example, suppose there is a "status" field in the second version of the target metamodel, which is used to describe the order status. The type of the "status" field is an enumeration, and its corresponding enumeration values ​​include: pending and completed. In the first version of the target metamodel, the enumeration values ​​corresponding to the "status" field include: pending, completed, and canceled. Then, it is determined that the metamodel change category corresponding to the change from the second version of the target metamodel to the first version of the target metamodel includes a change in the type value of the target field, specifically involving a change in the enumeration value of the "status" field.

[0078] The addition of target fields and the deletion of target fields, that is, the addition or deletion of certain fields in the process of changing the target metamodel of the second version to the target metamodel of the first version, will not be explained here with examples.

[0079] 302. Perform corresponding field change processing on the first modeling data according to the metamodel change category to generate second modeling data.

[0080] In an optional embodiment, if the metamodel change category is a type change of the target field, the first type corresponding to the target field in the first modeling data is changed to a second type to generate the second modeling data; if the metamodel change category is a type value change of the target field, the first type value corresponding to the target field in the first modeling data is changed to a second type value to generate the second modeling data. The first type and the first type value match the target metamodel of the first version, and the second type and the second type value match the target metamodel of the second version.

[0081] Assume that the metamodel change category is a type change of the target field, and take the type change of the above-mentioned "age" field as an example. In the specific implementation process, based on the metamodel change information, it has been known that the target metamodel of the second version has been changed to the target metamodel of the first version, and the type of the "age" field has been changed from an integer to a decimal. Based on this, the type corresponding to the "age" field in the first modeling data can be changed from a decimal to an integer, and the first modeling data after the change is the second modeling data. The change of the type value of the target field is similar to this, and will not be repeated here.

[0082] In another optional embodiment, if the meta-model change category is the addition of a target field, the remaining modeling data after filtering out the target field from the first modeling data is determined as the second modeling data.

[0083] For example, suppose the target metamodel of the second version includes: field 1, field 2 and field 3, and the target metamodel of the first version includes: field 1, field 2, field 3 and field 4, that is, when the second version changes to the first version, field 4 is added. Based on this, field 4 can be filtered out from the first modeling data, that is, the modeling data related to field 4 can be filtered out, and the remaining modeling data (that is, the modeling data associated with field 1, field 2 and field 3) is used as the second modeling data.

[0084] In yet another optional embodiment, if the metamodel change category is deletion of the target field, field information corresponding to the target field in the second version of the target metamodel is added to the first modeling data to generate the second modeling data.

[0085] For example, suppose that the target metamodel of the second version includes: field 1, field 2, field 3 and field 4, and the target metamodel of the first version includes: field 1, field 2 and field 3, that is, when the second version is changed to the first version, field 4 is deleted. It is easy to understand that in this case, the first modeling data does not include the modeling data associated with field 4, and the second modeling data to be generated needs to include the modeling data related to field 4. As an optional implementation method, the default field information corresponding to field 4 in the target metamodel of the second version can be used as the modeling data associated with field 4 and added to the first modeling data to generate the second modeling data; or, the modeling data configuration prompt information corresponding to field 4 is output, so as to obtain the modeling data corresponding to field 4 based on the configuration operation of the user of the first application modeling tool, and add the modeling data corresponding to field 4 to the first modeling data to generate the second modeling data.

[0086] In summary, the embodiments of the present application provide a plurality of schemes for generating second modeling data that match the metamodel change categories according to the metamodel change categories corresponding to the change of the target metamodel of the second version to the target metamodel of the first version, thereby enabling generation of second modeling data compatible with the target metamodel of a lower version based on the first modeling data compatible with the target metamodel of a higher version. Furthermore, when the target version corresponding to the target metamodel deployed in the second application construction tool is lower than the first version, the second application construction tool can be provided with modeling data compatible with the target metamodel of the target version, thereby realizing reuse of the modeling data of the target application component.

[0087] The above describes the corresponding data processing method when the version of the metamodel in the first application construction tool is higher than the version of the metamodel in the second application construction tool.

[0088] Next, the corresponding data processing method is described in the case where the version of the metamodel in the first application construction tool is lower than the version of the metamodel in the second application construction tool.

[0089] It is worth noting that, in the above embodiment, assuming that the target version corresponding to the target metamodel deployed in the second application construction tool is lower than the first version corresponding to the target metamodel deployed in the first application construction tool, in response to the modeling data request corresponding to the target application component sent by the second application construction tool, the first application construction tool can obtain target modeling data compatible with the target metamodel of the target version from the existing modeling data, thereby, the target data packet can be directly sent to the second application construction tool, or the target modeling data compatible with the target metamodel of the target version can be obtained from the target data packet first, and then the target modeling data can be sent to the second application construction tool.

[0090] However, when the target version is higher than the first version, the first application construction tool cannot obtain target modeling data compatible with the target metamodel of the target version from the existing modeling data, that is, it cannot obtain the target modeling data from the target data package. Based on this, optionally, if the first application construction tool determines that the target modeling data does not exist in the target data package, the target data package is sent to the second application construction tool, so that the second application construction tool builds the target application component based on the modeling data contained in the target data package.

[0091] Thus, in an embodiment of the present application, when the target version corresponding to the target metamodel deployed in the second application construction tool is higher than the first version corresponding to the target metamodel deployed in the first application construction tool, in response to the modeling data request corresponding to the target application component sent by the second application construction tool, the first application construction tool sends the target data packet to the second application construction tool.

[0092] Figure 4 An interactive flow chart of another data processing method provided in an embodiment of the present application, such as Figure 4 As shown, the following steps may be included: 401. In response to a construction operation of a target application component using a first version of a target metamodel, a first application construction tool obtains generated first modeling data.

[0093] 402. The first application construction tool determines a second version of the target metamodel based on pre-stored metamodel version information, where the second version is lower than the first version; and generates second modeling data corresponding to the first modeling data based on metamodel change information between the target metamodel of the first version and the target metamodel of the second version, where the second modeling data is compatible with the target metamodel of the second version.

[0094] 403. The first application construction tool generates a target data packet corresponding to the target application component, where the target data packet includes the first modeling data and the second modeling data.

[0095] 404. The second application construction tool sends a modeling data request corresponding to the target application component to the first application construction tool.

[0096] 405. The first application construction tool sends the target data packet to the second application construction tool in response to the modeling data request corresponding to the target application component.

[0097] 406. The second application construction tool obtains target modeling data compatible with the target metamodel of the target version from the target data package according to the target version corresponding to the target metamodel deployed by itself, and constructs the target application component based on the target modeling data.

[0098] The specific implementation process of step 401 to step 406 may refer to the aforementioned embodiment and will not be described in detail in this embodiment.

[0099] 407. If the target modeling data does not exist in the target data package, and the second application construction tool determines that the target version is higher than the first version based on the pre-stored metamodel version information, then according to the metamodel change information between the target metamodel of the first version and the target metamodel of the target version, third modeling data corresponding to the first modeling data is generated, and the third modeling data is compatible with the target metamodel of the target version.

[0100] 408. Build a target application component according to the third modeling data.

[0101] In the embodiment of the present application, it is assumed that the target version corresponding to the target metamodel deployed in the second application construction tool is higher than the first version corresponding to the target metamodel deployed in the first application construction tool.

[0102] It is easy to understand that the new version of the application construction tool can pre-store the metamodel information in the old version of the application construction tool, but the old version of the application construction tool is often difficult to obtain the metamodel information in the new version of the application construction tool. Therefore, in the process of the first application construction tool producing the modeling data corresponding to the target application component, it can generate modeling data that is compatible with the first version and the second version of the target metamodel that is lower than the first version, but it is difficult to generate modeling data that is compatible with the target metamodel of other versions higher than the first version. This also leads to the following situation in the reuse scenario of modeling data: when the target version corresponding to the target metamodel deployed in the second application construction tool is not higher than the first version, the target modeling data compatible with the target metamodel of the target version can be obtained from the target data package; when the target version is higher than the first version, the target modeling data cannot be obtained from the target data package, and the problem of not being able to reuse the modeling data of the target application component still occurs.

[0103] Based on this, an embodiment of the present application provides another data processing method. In summary: when the target modeling data does not exist in the target data packet and the target version is higher than the third version, the second application construction tool obtains the third modeling data that is compatible with the target metadata of the target version by upgrading the first modeling data in the target data packet, and can build the target application component based on the third modeling data, thereby solving the problem that the modeling data of the target application component cannot be reused when the target version is higher than the first version.

[0104] To elaborate, similar to the first application construction tool, the second application construction tool also pre-stores metamodel version information and metamodel change information. It is worth noting that the metamodel version information and metamodel change information stored in different versions of application construction tools are different. Application construction tools with higher versions store more metamodel version information and metamodel change information. For example, in a certain version of an application construction tool, only m lower versions of metamodel version information and metamodel change information corresponding to the target metamodel may be stored, while in other versions of application construction tools higher than this version, in addition to storing the m lower versions of metamodel version information and metamodel change information corresponding to the aforementioned target metamodel, n higher versions of metamodel version information and metamodel change information corresponding to the target metamodel may also be stored. Among them, m and n are positive integers.

[0105] Based on the metamodel version information and metamodel change information pre-stored in the second application construction tool, the second application construction tool can determine whether the target version is higher than the first version according to the metamodel version information when the target modeling data does not exist in the target data package. If it is higher than the first version, the third modeling data corresponding to the first modeling data is generated according to the metamodel change information between the target metamodel of the first version and the target metamodel of the target version. The third modeling data is compatible with the target metamodel of the target version.

[0106] As an optional way to generate the third modeling data, optionally, the metamodel change category corresponding to the change from the target metamodel of the first version to the target metamodel of the target version can be determined based on the metamodel change information between the target metamodel of the first version and the target metamodel of the target version. The metamodel change category includes at least one of the following: a change in the type of a target field, a change in the type value of a target field, an addition of a target field, and a deletion of a target field. Then, according to the metamodel change category, the first modeling data is processed with corresponding field changes to generate the third modeling data.

[0107] Among them, the metamodel change category corresponding to the change of the target metamodel of the first version to the target metamodel of the target version is also the metamodel change category corresponding to the upgrade of the target metamodel of the lower version to the target metamodel of the higher version. It is easy to understand that, when the modeling data compatible with the target metamodel of the lower version is known, and how the target metamodel of the lower version is changed to the target metamodel of the higher version, the modeling data compatible with the target metamodel of the higher version can naturally be obtained.

[0108] In an optional embodiment, if the metamodel change category is a type change of the target field, the first type corresponding to the target field in the first modeling data is changed to a third type to generate third modeling data; if the metamodel change category is a change of the type value of the target field, the first type value corresponding to the target field in the first modeling data is changed to a third type value to generate third modeling data; wherein the third type and the third type value match the target metamodel of the target version.

[0109] For example, Figure 3 In the embodiment, the type change of the "age" field is taken as an example. Assuming that the metamodel change category is the type change of the target field, based on the metamodel change information, it is determined that the target metamodel of the first version is changed to the target metamodel of the target version, which is to change the type of the "age" field from a decimal to a floating point number. Then, the type corresponding to the "age" field in the first modeling data can be changed from a decimal to a floating point number. The changed first modeling data is the third modeling data. The change of the type value of the target field is similar to this, and will not be repeated here.

[0110] In another optional embodiment, if the metamodel change category is the addition of a target field, field information corresponding to the target field in the target metamodel of the target version is added to the first modeling data to generate the third modeling data.

[0111] For example, suppose that the target metamodel of the first version includes: field 1, field 2 and field 3, and the target metamodel of the target version includes: field 1, field 2, field 3 and field 4, that is, when the first version is changed to the target version, field 4 is added or subtracted. It is easy to understand that in this case, the first modeling data does not include the modeling data associated with field 4, and the third modeling data to be generated needs to include the modeling data related to field 4. As an optional implementation method, the default field information corresponding to field 4 in the target metamodel of the target version can be used as the modeling data associated with field 4 and added to the first modeling data to generate the third modeling data; or, the modeling data configuration prompt information corresponding to field 4 is output, so as to obtain the modeling data corresponding to field 4 based on the configuration operation of the user of the second application modeling tool, and add the modeling data corresponding to field 4 to the first modeling data to generate the third modeling data.

[0112] In yet another optional embodiment, if the meta-model change category is deletion of the target field, the remaining modeling data after filtering out the target field from the first modeling data is determined as the third modeling data.

[0113] For example, assuming that the target metamodel of the first version includes: field 1, field 2, field 3 and field 4, and the target metamodel of the target version includes: field 1, field 2 and field 3, that is, when the first version is changed to the target version, field 4 is added. Based on this, field 4 can be filtered out from the first modeling data, that is, the modeling data related to field 4 can be filtered out, and the remaining modeling data (that is, the modeling data associated with field 1, field 2 and field 3) is used as the third modeling data.

[0114] It is worth noting that in the embodiment of the present application, the generation process of the second modeling data is: based on the modeling data compatible with the target metadata of the higher version, the modeling data compatible with the target metadata of the lower version is generated; the generation process of the third modeling data is: based on the modeling data compatible with the target metadata of the lower version, the modeling data compatible with the target metadata of the higher version is generated. In layman's terms, the generation process of the second modeling data and the third modeling data is a data conversion process in which the conversion directions of the two modeling data are opposite but the specific implementation process is similar. Since in the process of generating the second modeling data or the third modeling data, the metamodel change information pre-stored in the application construction tool is provided, the data change information of the first modeling data and the modeling data to be generated (i.e., the second modeling data or the third modeling data) is provided, so that, based on the metamodel change information and the first modeling data, the corresponding second modeling data or the third modeling data can be quickly generated.

[0115] Finally, the second application construction tool constructs the target application component according to the third modeling data.

[0116] To facilitate understanding, let's take an example to illustrate. Assume that the first version corresponding to the target metamodel deployed in the first application construction tool is V3.0, and the first application construction tool pre-stores metamodel version information indicating that the target metamodel has three versions, V3.0, VV2.0 and V1.0, of which V3.0 is the highest and V1.0 is the lowest; the target version corresponding to the target metamodel deployed in the second application construction tool is V4.0, where V4.0 is higher than V3.0.

[0117] Based on the above assumptions, in response to the construction operation of the target application component through the target metamodel of V3.0, the first application construction tool obtains the generated first modeling data (referred to as {modeling data, V3.0}), and then determines that the target metamodel has versions lower than V3.0, namely, V2.0 and V1.0, according to the pre-stored metamodel version information. Further, according to the pre-stored metamodel change information and {modeling data, V3.0}, {modeling data, V2.0} compatible with the target metamodel of V2.0 and {modeling data, V1.0} compatible with the target metamodel of V1.0 are generated respectively.

[0118] Furthermore, the first application construction tool generates a target data package corresponding to the target application component, and the target data package includes: {modeling data, V3.0}, {modeling data, V2.0} and {modeling data, V1.0}.

[0119] Next, when the second application construction tool wants to reuse the modeling data of the target application component, the second application construction tool sends a modeling data request corresponding to the target application component to the first application construction tool. In response to the modeling data request corresponding to the target application component, the first application construction tool sends the target data packet to the second application construction tool.

[0120] After receiving the target data package, the second application construction tool cannot obtain modeling data compatible with the target metamodel of V4.0 from the target data package because the target version corresponding to the target metamodel deployed by itself is V4.0.

[0121] Based on this, if the second application construction tool determines that V4.0 is higher than V3.0 based on the pre-stored metamodel version information, then based on the metamodel change information between the target metamodel of V3.0 and the target metamodel of V4.0, it generates {modeling data, V4.0} corresponding to {modeling data, V3.0}, where {modeling data, V4.0} is compatible with the target metamodel of V4.0.

[0122] Finally, the second application construction tool constructs the target application component according to {modeling data, V4.0}.

[0123] In summary, the data processing method provided by the embodiment of the present application, on the one hand, in the stage of the first application construction tool producing the modeling data of the target application component, not only the first modeling data corresponding to the target metamodel of the first version currently used is generated, but also the second modeling data corresponding to the target metamodel of the second version lower than the first version is generated, so that the target data packet corresponding to the further generated target application component contains multiple modeling data respectively compatible with the target metamodel of the first version and its lower versions. Thus, in the case where the target version corresponding to the target metamodel deployed in the second application construction tool is not higher than the first version, the second application construction tool can take the target modeling data compatible with the target metamodel of the target version from the target data packet containing multiple modeling data generated by the first application construction tool, and then build the target application component based on the target modeling data, so as to realize the reuse of the modeling data of the target application component. On the other hand, in the stage of the second application construction tool reusing the modeling data of the target application component, if the target version corresponding to the target metamodel deployed in the second application construction tool is higher than the first version, the first modeling data is upgraded to generate the third modeling data compatible with the target metamodel of the target version, and then build the target application component based on the third modeling data, so as to realize the reuse of the modeling data of the target application component. It can be seen that the data processing method provided in the embodiment of the present application can realize the reuse of modeling data of the target application component when the target metamodel versions used to construct the target application component in the first application construction tool and the second application construction tool are inconsistent.

[0124] In actual applications, the first application construction tool may construct multiple different application components, and the same application component may also have multiple different versions. It is easy to understand that each version of the application component has a corresponding data package. In order to ensure that the second modeling tool can determine the target application component that matches its own application construction requirements from multiple different application components with different versions, and obtain the target data package corresponding to the target application component, the embodiment of the present application provides a target application component recommendation method.

[0125] Figure 5 An interactive flow chart of a target application component recommendation method provided in an embodiment of the present application, such as Figure 5 As shown, the following steps may be included: 501. A first application construction tool generates target description information corresponding to a target data packet of a target application component. The target description information includes at least one of the following: a function of the target application component and an application field of the target application component.

[0126] 502. The second application building tool sends an application building requirement to the first modeling tool.

[0127] 503. If the first application construction tool determines that the target description information matches the application construction requirement, the first application construction tool sends recommendation information corresponding to the target application component to the second application construction tool.

[0128] 504. The second application construction tool receives recommendation information corresponding to the target application component, and sends a modeling data request corresponding to the target application component to the first application construction tool according to the recommendation information corresponding to the target application component.

[0129] In the embodiment of the present application, taking the target application component as an example, the process of generating data packets of different application components of different versions is explained.

[0130] In the specific implementation process, after generating the target data packet corresponding to the target application component, further, target description information corresponding to the target data packet can be generated. The target description information is also the label information or introduction information corresponding to the target application component, which is used to assist the user of the second application construction tool to select the corresponding application component and data packet from different application components of different versions. Optionally, the target description information includes at least one of the following: the function of the target application component, the application field of the target application component.

[0131] The functions of application components refer to the specific tasks that application components undertake in the application program, such as the functions of user authentication components: processing user login, registration, password reset, etc. The functions of payment processing components: processing payment requests, interacting with payment gateways, recording transaction information, returning payment results, etc. The application fields of application components refer to the industry fields in which application components are applied, including but not limited to e-commerce, healthcare, finance, education, entertainment, etc.

[0132] Based on the description information corresponding to each application component, the user of the second application construction tool can manually select the target application component that he needs to build and obtain the modeling data corresponding to the target application component. In the embodiment of the present application, in order to improve the accuracy and convenience of the user of the second application construction tool in obtaining the modeling data corresponding to the target application component, an automated recommendation method is also provided.

[0133] Specifically, when the second application construction tool needs to construct a certain application component by reusing modeling data, it sends an application construction requirement to the first modeling tool, and the application construction requirement may include the functions to be implemented, application fields, etc. Therefore, after receiving the application construction requirement, the first application construction tool may match the application construction requirement with the description information corresponding to different application components.

[0134] Optionally, the matching result between the application construction requirement and the description information corresponding to different application components can be determined by calculating, for example, cosine similarity between the application construction requirement and the description information corresponding to different application components. For example, if the similarity between the application construction requirement and the description information corresponding to a certain application component is greater than a set threshold, it is determined that the application construction requirement matches the description information corresponding to the application component.

[0135] If the first application construction tool determines that the target component target description information matches the application construction requirements, it sends the recommendation information corresponding to the target application component to the second application construction tool. After receiving the recommendation information corresponding to the target application component, the second application construction tool sends the modeling data request corresponding to the target application component to the first application construction tool according to the recommendation information corresponding to the target application component.

[0136] In an embodiment of the present application, an automated target application component recommendation method is provided by generating target description information corresponding to a target data packet of a target application component, and when it is determined that the target description information matches the application construction requirements, sending recommendation information corresponding to the target application component to a second application construction tool. This method can effectively improve the accuracy and convenience of users of the second application construction tool in obtaining modeling data corresponding to the target application component.

[0137] In practical applications, such as Figure 1As shown, the first application construction tool and the second application construction tool in the embodiment of the present application are two independently deployed application construction tools. Among them, the communication connection between the VPC or private cloud used for the first application construction tool and the second application construction tool can be connected or disconnected. Correspondingly, there may be an information transmission channel between the first application construction tool and the second application construction tool, or there may not be an information transmission channel.

[0138] It is understandable that when there is an information transmission channel between the first application construction tool and the second application construction tool, the second application construction tool can directly obtain the target data packet corresponding to the target application component online from the first application construction tool by, for example, online subscription. When there is no information transmission channel between the first application construction tool and the second application construction tool, if the second application construction tool wants to obtain the target data packet corresponding to the target application component, the first application construction tool needs to first export the offline target data packet corresponding to the target application component, and then transmit the offline target data packet to the second application construction tool by offline transmission, etc., and then the second application construction tool imports the offline target data packet.

[0139] In order to improve the convenience of the second application construction tool to obtain the target data packet corresponding to the target application component, the embodiment of the present application provides the following Figure 6 The target data packet acquisition method shown.

[0140] Figure 6 An interactive flow chart of a method for acquiring a target data packet provided in an embodiment of the present application, such as Figure 6 As shown, the following steps may be included: 601. The first application construction tool transmits a target data packet corresponding to a target application component and / or target description information corresponding to the target data packet to a third-party platform, where the target description information includes a download path of the target data packet.

[0141] 602. The second application construction tool sends a modeling data request corresponding to the target application component to the third-party platform.

[0142] 603. The second application construction tool receives a target data packet corresponding to a target application component fed back by the third-party platform.

[0143] In the embodiment of the present application, there are information transmission channels between the third-party platform and both the first application construction tool and the second application construction tool. By sending the target data corresponding to the target application component to the third-party platform, the second application construction tool can quickly and conveniently obtain the target data packet corresponding to the target application component from the third-party platform when there is no information transmission channel between the first application construction tool and the second application construction tool.

[0144] Optionally, in actual applications, the target data packet corresponding to the target application component may not be transmitted to the third-party platform, but the target description information corresponding to the target data packet may be transmitted to the third-party platform. Optionally, the target description information may include a download path corresponding to the target data packet. Thus, the third-party platform may feed back the download path to the second application construction tool so that it obtains the target data packet corresponding to the target application component according to the download path; or, the third-party platform obtains the target data packet corresponding to the target application component according to the download path, and forwards the target data packet to the second application construction tool.

[0145] Optionally, the target description information corresponding to the target data packet may also include at least one of the following: the function of the target application component, the application field of the target application component. Based on the description information corresponding to different application components in the third-party platform, the target application component matching its application construction requirements may be recommended to the second application construction tool so that it generates a modeling data request corresponding to the target application component. The specific implementation process can be referred to Figure 5 The embodiments are not described in detail here.

[0146] In an embodiment of the present application, there is an information transmission channel between the third-party platform and the first application construction tool and the second application construction tool. By transmitting the target data packet corresponding to the target application component and / or the target description information corresponding to the target data packet to the third-party platform, a new method of obtaining the target data packet of the target application component is provided, thereby improving the convenience for the second application construction tool to obtain the target data packet corresponding to the target application component when there is no information transmission channel between the first application construction tool and the second application construction tool.

[0147] Figure 7 is a flow chart of the data processing method provided in the embodiment of the present application when it is executed on the first application construction tool side. The first application construction tool is deployed with a set of metamodels for building different application components, such as Figure 7 As shown, the following steps may be included: 701. In response to a construction operation of a target application component using a first version of a target metamodel, first generated modeling data is acquired, wherein a metamodel set includes the first version of the target metamodel.

[0148] 702. Determine a second version of the target metamodel according to pre-stored metamodel version information, where the second version is lower than the first version.

[0149] 703. Generate second modeling data corresponding to the first modeling data according to the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, wherein the second modeling data is compatible with the target metamodel of the second version.

[0150] 704. In response to a modeling data request corresponding to a target application component sent by the second application construction tool, the target modeling data is sent to the second application construction tool, so that the second application construction tool constructs the target application component based on the target modeling data, the target modeling data is compatible with a target version corresponding to a target metamodel deployed in the second application construction tool, and the first modeling data and the second modeling data include the target modeling data.

[0151] In an optional embodiment, after generating the second modeling data corresponding to the first modeling data, it also includes: generating a target data packet corresponding to the target application component, the target data packet including the first modeling data and the second modeling data. Correspondingly, in response to a modeling data request corresponding to the target application component sent by the second application construction tool, the target modeling data is sent to the second application construction tool so that the second application construction tool constructs the target application component based on the target modeling data, including: in response to a modeling data request corresponding to the target application component sent by the second application construction tool, the target data packet is sent to the second application construction tool so that the second application construction tool obtains the target modeling data from the target data packet and constructs the target application component based on the target modeling data; or, in response to a modeling data request corresponding to the target application component sent by the second application construction tool, the target modeling data is obtained from the target data packet and sent to the second application construction tool so that the second application construction tool constructs the target application component based on the target modeling data.

[0152] In an optional embodiment, second modeling data corresponding to the first modeling data is generated according to metamodel change information between the target metamodel of the first version and the target metamodel of the second version, including: determining the metamodel change category corresponding to the change of the target metamodel of the second version to the target metamodel of the first version according to the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, the metamodel change category including at least one of the following: type change of the target field, change of the type value of the target field, addition of the target field, and deletion of the target field; and performing corresponding field change processing on the first modeling data according to the metamodel change category to generate the second modeling data.

[0153] In an optional embodiment, according to the metamodel change category, corresponding field change processing is performed on the first modeling data to generate second modeling data, including: if the metamodel change category is a type change of the target field, the first type corresponding to the target field in the first modeling data is changed to a second type to generate the second modeling data; if the metamodel change category is a change of the type value of the target field, the first type value corresponding to the target field in the first modeling data is changed to a second type value to generate the second modeling data; wherein the second type and the second type value match the target metamodel of the second version; if the metamodel change category is an addition of the target field, the remaining modeling data after filtering out the target field from the first modeling data is determined as the second modeling data; if the metamodel change category is a deletion of the target field, the field information corresponding to the target field in the target metamodel of the second version is added to the first modeling data to generate the second modeling data.

[0154] In an optional embodiment, after generating a target data packet corresponding to the target application component, the method further includes: generating target description information corresponding to the target data packet, the target description information including at least one of the following: the function of the target application component, the application field of the target application component; if, based on the application construction requirements sent by the second application construction tool, it is determined that the target description information matches the application construction requirements, then sending recommendation information corresponding to the target application component to the second application construction tool, so that the second application construction tool sends a modeling data request corresponding to the target application component according to the recommendation information.

[0155] In an optional embodiment, after generating a target data packet corresponding to the target application component, the method further includes: transmitting target description information corresponding to the target data packet and / or the target data to a third-party platform, so that the second application construction tool obtains the target data packet through the third-party platform, and the target description information includes a download path of the target data packet.

[0156] Figure 8 is a flow chart of the data processing method provided in the embodiment of the present application when it is executed on the second application construction tool side. The second application construction tool is deployed with a set of metamodels for building different application components, such as Figure 8 As shown, the following steps may be included: 801. Send a modeling data request corresponding to a target application component to a first application construction tool, where the target application component is constructed by the first application construction tool using a first version of a target metamodel.

[0157] 802. Receive target modeling data corresponding to a target application component sent by a first application modeling tool, the target modeling data being compatible with a target version corresponding to a target metamodel included in a metamodel set, the target modeling data being included in first modeling data and second modeling data, the first modeling data being modeling data acquired by the first application construction tool in response to a construction operation on the target application component, the second modeling data being generated based on the first modeling data, the second modeling data being compatible with a second version of the target metamodel, and the second version being lower than the first version.

[0158] 803. Build target application components according to target modeling data.

[0159] In an optional embodiment, receiving target modeling data sent by a first application modeling tool includes: receiving a target data packet sent by the first application modeling tool, the target data packet including first modeling data and second modeling data; and obtaining target modeling data compatible with the target metamodel of the target version from the target data packet according to a target version corresponding to a target metamodel included in a metamodel set.

[0160] In an optional embodiment, if the target modeling data does not exist in the target data packet, and it is determined that the target version is higher than the first version based on the pre-stored metamodel version information, then third modeling data corresponding to the first modeling data is generated based on the metamodel change information between the target metamodel of the first version and the target metamodel of the target version, and the third modeling data is compatible with the target metamodel of the target version; and the target application component is constructed based on the third modeling data.

[0161] In an optional embodiment, generating third modeling data corresponding to the first modeling data according to metamodel change information between a target metamodel of the first version and a target metamodel of the target version includes: determining a metamodel change category corresponding to the change from the target metamodel of the first version to the target metamodel of the target version according to the metamodel change information between the target metamodel of the first version and the target metamodel of the target version, wherein the metamodel change category includes at least one of the following: a type change of a target field, a change of a type value of a target field, an addition of a target field, and a deletion of a target field; performing corresponding field change processing on the first modeling data according to the metamodel change category to generate the third modeling data; if the metamodel change category is a type change of the target field, changing the first type corresponding to the target field in the first modeling data to a third type to generate the third modeling data; if the metamodel change category is a type value change of the target field, changing the first type value corresponding to the target field in the first modeling data to a third type value to generate the third modeling data; wherein the third type and the third type value match the target metamodel of the target version.

[0162] In an optional embodiment, according to the metamodel change category, corresponding field change processing is performed on the first modeling data to generate third modeling data, and it also includes: if the metamodel change category is the addition of a target field, the field information corresponding to the target field in the target metamodel of the target version is added to the first modeling data to generate the third modeling data; if the metamodel change category is the deletion of the target field, the remaining modeling data after filtering out the target field from the first modeling data is determined as the third modeling data.

[0163] In an optional embodiment, before sending a modeling data request corresponding to the target application component to the first application construction tool, the method also includes: sending application construction requirements to the first modeling tool; receiving recommendation information corresponding to the target application component sent by the first modeling tool when determining that the application construction requirements match the target description information; the target description information is the description information of the target data packet corresponding to the target application component, and the target description information includes at least one of the following: the function of the target application component, the application field of the target application component.

[0164] In an optional embodiment, the method also includes: sending a modeling data request corresponding to the target application component to a third-party platform, the third-party platform stores the target data packet uploaded by the first application construction tool and / or target description information corresponding to the target data packet, the target description information including the download path of the target data packet; receiving the target data packet corresponding to the target application component fed back by the third-party platform.

[0165] The data processing device of one or more embodiments of the present application will be described in detail below. Those skilled in the art will appreciate that these devices can be configured using commercially available hardware components through the steps taught in this solution.

[0166] Fig. 9 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application is applied to a first application construction tool, wherein a set of metamodels for constructing different application components is deployed in the first application construction tool, such as Fig. 9 As shown, the device includes: a first acquisition module 11, a first processing module 12, and a first sending module 13.

[0167] The first acquisition module 11 is used to acquire the generated first modeling data in response to the construction operation of the target application component through the first version of the target metamodel, and the metamodel set includes the first version of the target metamodel.

[0168] The first processing module 12 is used to determine the second version of the target metamodel based on pre-stored metamodel version information, the second version is lower than the first version; and generate second modeling data corresponding to the first modeling data based on the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, the second modeling data is compatible with the target metamodel of the second version.

[0169] The first sending module 13 is used to respond to a modeling data request corresponding to the target application component sent by the second application construction tool, and send the target modeling data to the second application construction tool, so that the second application construction tool builds the target application component based on the target modeling data, the target modeling data is compatible with the target version corresponding to the target metamodel deployed in the second application construction tool, and the first modeling data and the second modeling data include the target modeling data.

[0170] In an optional embodiment, the first processing module 12 is further configured to generate a target data packet corresponding to the target application component, wherein the target data packet includes the first modeling data and the second modeling data.

[0171] Correspondingly, when the first sending module 13 sends the target modeling data to the second application construction tool in response to the modeling data request corresponding to the target application component sent by the second application construction tool, so that the second application construction tool constructs the target application component based on the target modeling data, it is specifically used to send the target data packet to the second application construction tool in response to the modeling data request corresponding to the target application component sent by the second application construction tool, so that the second application construction tool obtains the target modeling data from the target data packet and constructs the target application component based on the target modeling data; or, in response to the modeling data request corresponding to the target application component sent by the second application construction tool, obtain the target modeling data from the target data packet and send the target modeling data to the second application construction tool, so that the second application construction tool constructs the target application component based on the target modeling data.

[0172] When generating second modeling data corresponding to the first modeling data according to the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, the first processing module 12 is specifically used to: determine the metamodel change category corresponding to the change of the target metamodel of the second version to the target metamodel of the first version according to the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, wherein the metamodel change category includes at least one of the following: type change of the target field, change of the type value of the target field, addition of the target field, and deletion of the target field; and perform corresponding field change processing on the first modeling data according to the metamodel change category to generate the second modeling data.

[0173] In an optional embodiment, when the first processing module 12 performs corresponding field change processing on the first modeling data according to the metamodel change category to generate the second modeling data, it is specifically used to: if the metamodel change category is a type change of the target field, then the first type corresponding to the target field in the first modeling data is changed to a second type to generate the second modeling data; if the metamodel change category is a change of the type value of the target field, then the first type value corresponding to the target field in the first modeling data is changed to a second type value to generate the second modeling data; wherein the second type and the second type value match the target metamodel of the second version; if the metamodel change category is an addition of a target field, then the remaining modeling data after filtering out the target field from the first modeling data is determined as the second modeling data; if the metamodel change category is a deletion of the target field, then the field information corresponding to the target field in the target metamodel of the second version is added to the first modeling data to generate the second modeling data.

[0174] In an optional embodiment, after generating the target data packet corresponding to the target application component, the first processing module 12 is further used to: generate target description information corresponding to the target data packet, the target description information including at least one of the following: the function of the target application component, the application field of the target application component; if it is determined that the target description information matches the application construction requirement according to the application construction requirement sent by the second application construction tool, then send recommendation information corresponding to the target application component to the second application construction tool, so that the second application construction tool sends a modeling data request corresponding to the target application component according to the recommendation information.

[0175] In an optional embodiment, after generating the target data packet corresponding to the target application component, the first processing module 12 is further used to: transmit the target data packet and / or the target description information corresponding to the target data packet to a third-party platform, so that the second application construction tool obtains the target data packet through the third-party platform, and the target description information includes the download path of the target data packet.

[0176] In an optional embodiment, the first application construction tool and the second application construction tool are respectively deployed in different virtual private clouds in a public cloud, or the first application construction tool and the second application construction tool are respectively deployed in different private clouds, or one of the first application construction tool and the second application construction tool is deployed in a virtual private cloud in a public cloud, and the other is deployed in a private cloud.

[0177] Fig. 9 The device shown can execute the steps introduced in the aforementioned embodiments. For detailed execution process and technical effects, please refer to the description in the aforementioned embodiments, which will not be repeated here.

[0178] Fig.10 A schematic diagram of the structure of another data processing device provided in an embodiment of the present application is applied to a second application construction tool, in which a set of metamodels for constructing different application components is deployed, such as Fig.10 As shown, the device includes: a second sending module 21, a second acquiring module 22, and a second processing module 23.

[0179] The second sending module 21 is used to send a modeling data request corresponding to a target application component to the first application construction tool, where the target application component is constructed by the first application construction tool using a first version of the target metamodel.

[0180] The second acquisition module 22 is used to receive target modeling data sent by the first application modeling tool, the target modeling data is compatible with the target version corresponding to the target metamodel contained in the metamodel set, the target modeling data is included in the first modeling data and the second modeling data, the first modeling data is the modeling data acquired by the first application construction tool in response to the construction operation of the target application component, the second modeling data is generated based on the first modeling data, the second modeling data is compatible with the second version of the target metamodel, and the second version is lower than the first version.

[0181] The second processing module 23 is used to construct the target application component according to the target modeling data.

[0182] In an optional embodiment, when receiving the target modeling data sent by the first application modeling tool, the second acquisition module 22 is specifically used to receive a target data packet sent by the first application modeling tool, wherein the target data packet includes the first modeling data and the second modeling data; and according to the target version corresponding to the target metamodel included in the metamodel set, obtain the target modeling data compatible with the target metamodel of the target version from the target data packet.

[0183] In an optional embodiment, the second acquisition module 22 is also used for: if the target modeling data does not exist in the target data packet, and based on the pre-stored metamodel version information, it is determined that the target version is higher than the first version, then, based on the metamodel change information between the target metamodel of the first version and the target metamodel of the target version, generating third modeling data corresponding to the first modeling data, wherein the third modeling data is compatible with the target metamodel of the target version.

[0184] Correspondingly, the second processing module 23 is further used to construct the target application component according to the third modeling data.

[0185] In an optional embodiment, when the second acquisition module 22 generates the third modeling data corresponding to the first modeling data according to the metamodel change information between the target metamodel of the first version and the target metamodel of the target version, it is specifically used to: determine the metamodel change category corresponding to the change of the target metamodel of the first version to the target metamodel of the target version according to the metamodel change information between the target metamodel of the first version and the target metamodel of the target version, the metamodel change category including at least one of the following: type change of the target field, change of the type value of the target field, addition of the target field, deletion of the target field; and perform corresponding field change processing on the first modeling data according to the metamodel change category to generate the third modeling data.

[0186] In an optional embodiment, when the second acquisition module 22 performs corresponding field change processing on the first modeling data according to the metamodel change category to generate the third modeling data, it is specifically used to: if the metamodel change category is a type change of the target field, then the first type corresponding to the target field in the first modeling data is changed to a third type to generate the third modeling data; if the metamodel change category is a change of the type value of the target field, then the first type value corresponding to the target field in the first modeling data is changed to a third type value to generate the third modeling data; wherein the third type and the third type value match the target metamodel of the target version; if the metamodel change category is an addition of a target field, then the field information corresponding to the target field in the target metamodel of the target version is added to the first modeling data to generate the third modeling data; if the metamodel change category is a deletion of the target field, then the remaining modeling data after filtering out the target field from the first modeling data is determined as the third modeling data.

[0187] In an optional embodiment, before sending the modeling data request corresponding to the target application component to the first application building tool, the second sending module 21 is further used to: send an application building requirement to the first modeling tool.

[0188] Correspondingly, the second acquisition module 22 is also used to: receive recommendation information corresponding to the target application component sent by the first modeling tool when determining that the application construction requirements match the target description information; the target description information is the description information of the target data packet corresponding to the target application component, and the target description information includes at least one of the following: the function of the target application component, and the application field of the target application component.

[0189] In an optional embodiment, the second sending module 21 is also used to: send a modeling data request corresponding to the target application component to a third-party platform, and the third-party platform stores the target data packet uploaded by the first application construction tool and / or the target description information corresponding to the target data packet, and the target description information includes the download path of the target data packet.

[0190] Correspondingly, the second acquisition module 22 is further used to: receive the target data packet corresponding to the target application component fed back by the third-party platform.

[0191] In an optional embodiment, the first application construction tool and the second application construction tool are respectively deployed in different virtual private clouds in a public cloud, or the first application construction tool and the second application construction tool are respectively deployed in different private clouds, or one of the first application construction tool and the second application construction tool is deployed in a virtual private cloud in a public cloud, and the other is deployed in a private cloud.

[0192] Fig.10 The device shown can execute the steps introduced in the aforementioned embodiments. For detailed execution process and technical effects, please refer to the description in the aforementioned embodiments, which will not be repeated here.

[0193] In one possible design, the above Fig. 9 or Fig.10 The structure of the data processing device shown can be implemented as an electronic device, such as Fig.11 As shown, the electronic device may include: a memory 31, a processor 32, and a communication interface 33. The memory 31 stores a computer program, and when the computer program is executed by the processor 32, the processor 32 can at least implement the data processing method provided in the above embodiments.

[0194] The above-mentioned memory 31 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0195] Accordingly, the embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the processor is enabled to implement each step in the above method embodiment. Among them, the computer-readable storage medium includes volatile or non-volatile or a combination thereof, and can be removable or non-removable. Examples of computer-readable storage media include, but are not limited to, phase-change random access memory (Phase-change Random Access Memory, PRAM), static random access memory (SRAM), dynamic random access memory (Dynamic Random Access Memory, DRAM), other types of random access memory (Random-Access Memory, RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), flash memory or other memory technology, read-only compact disc read-only memory (CD-ROM), digital versatile disc (Digital Video Disc, DVD) or other optical storage, magnetic cassette, tape disk storage or other magnetic storage device or any other non-transmission medium Accordingly, the present application embodiment also provides a computer program product, the computer program product includes a computer program or an instruction, when the computer program or the instruction is executed by the processor, the processor is enabled to implement each step in the above method embodiment. It should be understood that each process or a combination of multiple processes in the above method flow can be implemented by a computer program or an instruction. In addition, these computer programs or instructions can be applied to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device, so that the processor of the general-purpose computer, the special-purpose computer, the embedded processor or other programmable data processing device can be implemented as a device for implementing the corresponding functions in the above method embodiment.

[0196] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. Those of ordinary skill in the art may understand and implement the present invention without creative effort.

[0197] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by adding a necessary general hardware platform, and of course can also be implemented by combining hardware and software. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a computer product, and the present application can be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0198] Finally, it should be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device that includes a series of elements includes not only those elements, but also other elements that are not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device that includes the elements.

[0199] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A data processing method, characterized in that: Applied to a first application construction tool, in which a set of metamodels for constructing different application components is deployed, the method comprises: In response to a construction operation of a target application component through a first version of a target metamodel, obtaining generated first modeling data, wherein the metamodel set includes the first version of the target metamodel; Determining a second version of the target metamodel according to pre-stored metamodel version information, where the second version is lower than the first version; generating second modeling data corresponding to the first modeling data according to metamodel change information between the first version of the target metamodel and the second version of the target metamodel, wherein the second modeling data is compatible with the second version of the target metamodel; In response to a modeling data request corresponding to the target application component sent by a second application construction tool, target modeling data is sent to the second application construction tool so that the second application construction tool builds the target application component based on the target modeling data, the target modeling data is compatible with a target version corresponding to a target metamodel deployed in the second application construction tool, and the first modeling data and the second modeling data include the target modeling data.

2. The method according to claim 1, characterized in that: After generating second modeling data corresponding to the first modeling data, the method further includes: Generate a target data packet corresponding to the target application component, wherein the target data packet includes the first modeling data and the second modeling data; The step of sending the target modeling data to the second application construction tool in response to the modeling data request corresponding to the target application component sent by the second application construction tool, so that the second application construction tool constructs the target application component based on the target modeling data, includes: In response to a modeling data request corresponding to the target application component sent by a second application construction tool, sending the target data packet to the second application construction tool, so that the second application construction tool obtains the target modeling data from the target data packet and constructs the target application component based on the target modeling data; or In response to a modeling data request corresponding to the target application component sent by the second application construction tool, the target modeling data is obtained from the target data packet, and the target modeling data is sent to the second application construction tool, so that the second application construction tool constructs the target application component based on the target modeling data.

3. The method according to claim 1, characterized in that The generating, according to the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, the second modeling data corresponding to the first modeling data includes: Determine, according to the metamodel change information between the target metamodel of the first version and the target metamodel of the second version, a metamodel change category corresponding to the change of the target metamodel of the second version to the target metamodel of the first version, wherein the metamodel change category includes at least one of the following: a type change of a target field, a change of a type value of a target field, an addition of a target field, and a deletion of a target field; According to the metamodel change category, corresponding field change processing is performed on the first modeling data to generate the second modeling data.

4. The method according to claim 3, characterized in that The performing corresponding field change processing on the first modeling data according to the metamodel change category to generate the second modeling data includes: If the metamodel change category is a type change of the target field, changing the first type corresponding to the target field in the first modeling data to a second type to generate the second modeling data; If the metamodel change category is a change in the type value of the target field, then changing the first type value corresponding to the target field in the first modeling data to a second type value to generate the second modeling data; wherein the second type and the second type value match the target metamodel of the second version; If the meta-model change category is the addition of a target field, determining the remaining modeling data after filtering out the target field from the first modeling data as the second modeling data; If the meta-model change category is deletion of the target field, field information corresponding to the target field in the second version of the target meta-model is added to the first modeling data to generate the second modeling data.

5. The method according to claim 2, characterized in that: After generating the target data packet corresponding to the target application component, the method further includes: Generate target description information corresponding to the target data packet, wherein the target description information includes at least one of the following: a function of the target application component and an application field of the target application component; If it is determined that the target description information matches the application construction requirement sent by the second application construction tool, recommendation information corresponding to the target application component is sent to the second application construction tool, so that the second application construction tool sends a modeling data request corresponding to the target application component according to the recommendation information.

6. The method according to claim 2, characterized in that After generating the target data packet corresponding to the target application component, the method further includes: The target data packet and / or the target description information corresponding to the target data packet is transmitted to a third-party platform, so that the second application construction tool obtains the target data packet through the third-party platform, and the target description information includes a download path of the target data packet.

7. The method according to any one of claims 1 to 6, characterized in that The first application construction tool and the second application construction tool are respectively deployed in different virtual private clouds in a public cloud, or the first application construction tool and the second application construction tool are respectively deployed in different proprietary clouds, or one of the first application construction tool and the second application construction tool is deployed in a virtual private cloud in a public cloud, and the other is deployed in a proprietary cloud.

8. A data processing method, characterized in that: Applied to a second application construction tool, in which a set of metamodels for constructing different application components is deployed, the method comprises: Sending a modeling data request corresponding to a target application component to a first application construction tool, wherein the target application component is constructed by the first application construction tool using a first version of a target metamodel; receiving target modeling data sent by the first application modeling tool, the target modeling data being compatible with a target version corresponding to the target metamodel included in the metamodel set, the target modeling data being included in first modeling data and second modeling data, the first modeling data being modeling data acquired by the first application building tool in response to a building operation on the target application component, the second modeling data being generated based on the first modeling data, the second modeling data being compatible with a second version of the target metamodel, the second version being lower than the first version; The target application component is constructed according to the target modeling data.

9. The method according to claim 8, characterized in that The receiving the target modeling data sent by the first application modeling tool includes: receiving a target data packet sent by the first application modeling tool, wherein the target data packet includes the first modeling data and the second modeling data; According to the target version corresponding to the target metamodel contained in the metamodel set, target modeling data compatible with the target metamodel of the target version is acquired from the target data packet.

10. The method according to claim 9, characterized in that The method further comprises: If the target modeling data does not exist in the target data packet, and it is determined according to the pre-stored metamodel version information that the target version is higher than the first version, generating third modeling data corresponding to the first modeling data according to the metamodel change information between the target metamodel of the first version and the target metamodel of the target version, wherein the third modeling data is compatible with the target metamodel of the target version; The target application component is constructed according to the third modeling data.

11. The method according to claim 10, characterized in that The step of generating third modeling data corresponding to the first modeling data according to the metamodel change information between the target metamodel of the first version and the target metamodel of the target version includes: Determining, according to metamodel change information between the target metamodel of the first version and the target metamodel of the target version, a metamodel change category corresponding to the change from the target metamodel of the first version to the target metamodel of the target version, wherein the metamodel change category includes at least one of the following: a type change of a target field, a change of a type value of a target field, an addition of a target field, and a deletion of a target field; According to the metamodel change category, corresponding field change processing is performed on the first modeling data to generate the third modeling data.

12. The method according to claim 11, characterized in that The performing corresponding field change processing on the first modeling data according to the metamodel change category to generate the third modeling data includes: If the metamodel change category is a type change of the target field, changing the first type corresponding to the target field in the first modeling data to a third type to generate the third modeling data; If the metamodel change category is a change in the type value of the target field, then changing the first type value corresponding to the target field in the first modeling data to a third type value to generate the third modeling data; wherein the third type and the third type value match the target metamodel of the target version; If the metamodel change category is the addition of a target field, adding field information corresponding to the target field in the target metamodel of the target version to the first modeling data to generate the third modeling data; If the meta-model change category is deletion of a target field, the remaining modeling data after filtering out the target field from the first modeling data is determined as the third modeling data.

13. The method according to claim 9, characterized in that Before sending the modeling data request corresponding to the target application component to the first application building tool, the method further includes: Sending an application building requirement to the first modeling tool; Receive recommendation information corresponding to the target application component sent by the first modeling tool when determining that the application construction requirements match the target description information; the target description information is description information of the target data packet corresponding to the target application component, and the target description information includes at least one of the following: the function of the target application component and the application field of the target application component.

14. The method according to claim 9, characterized in that The method further comprises: Sending a modeling data request corresponding to a target application component to a third-party platform, wherein the third-party platform stores the target data packet uploaded by the first application building tool and / or target description information corresponding to the target data packet, wherein the target description information includes a download path of the target data packet; Receive a target data packet corresponding to the target application component fed back by the third-party platform.

15. The method according to any one of claims 8 to 14, characterized in that The first application construction tool and the second application construction tool are respectively deployed in different virtual private clouds in a public cloud, or the first application construction tool and the second application construction tool are respectively deployed in different proprietary clouds, or one of the first application construction tool and the second application construction tool is deployed in a virtual private cloud in a public cloud, and the other is deployed in a proprietary cloud.

16. An electronic device, characterized in that: include: A memory, a processor, and a communication interface; wherein a computer program is stored on the memory, and when the computer program is executed by the processor, the processor executes the data processing method as described in any one of claims 1 to 7, or the data processing method as described in any one of claims 8 to 15.

17. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor of an electronic device, the processor executes the data processing method as described in any one of claims 1 to 7, or the data processing method as described in any one of claims 8 to 15.

18. A computer program product, characterized in that include: A computer program or instruction, when the computer program or instruction is executed by a processor of an electronic device, causes the processor to execute the data processing method as described in any one of claims 1 to 7, or the data processing method as described in any one of claims 8 to 15.

Images