CN111984240A - Method and device for expanding public service logic of domain entity - Google Patents
Method and device for expanding public service logic of domain entity Download PDFInfo
- Publication number
- CN111984240A CN111984240A CN202010603404.5A CN202010603404A CN111984240A CN 111984240 A CN111984240 A CN 111984240A CN 202010603404 A CN202010603404 A CN 202010603404A CN 111984240 A CN111984240 A CN 111984240A
- Authority
- CN
- China
- Prior art keywords
- type
- entity
- metadata
- interface
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 238000011068 loading method Methods 0.000 claims description 7
- 238000011161 development Methods 0.000 abstract description 15
- 238000013461 design Methods 0.000 abstract description 3
- 239000000463 material Substances 0.000 description 6
- 238000013507 mapping Methods 0.000 description 5
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000009417 prefabrication Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 239000006185 dispersion Substances 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/313—Logic programming, e.g. PROLOG programming language
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method and a device for expanding public service logic of a domain entity, which are used for solving the problems that in domain-driven design and development, the service logic has strong dispersity, repeated development is easily caused, and extra workload of developers is increased. The method comprises the steps of determining an interface standard of a preset type; the type represents the public service logic of the entity, and the interface standard comprises type metadata information, a type metadata operation interface and an entity metadata type operation interface; calling the type metadata operation interface to acquire type information; and calling the entity metadata version operation interface according to the acquired version information, and determining a version corresponding to the version information added or removed from the entity to be operated.
Description
Technical Field
The present application relates to the field of software development technologies, and in particular, to a method and an apparatus for extending a public service logic of a domain entity.
Background
In domain-driven design development, entities in various domains often have similar business logic. For example, in an Enterprise Resource Planning (ERP) system, the business logic related to the material in the purchasing process needs to be agreed with the business logic related to the material in the receiving process.
At present, in the process of software development, developers usually need to set business logic of entities in each field respectively. Moreover, when the business logic of an entity is modified, the business logic of the associated entity needs to be modified together.
However, in the process of modifying the similar business logic of the entity respectively, the high dispersion of the business logic not only brings a large workload, but also easily causes omission, errors and the like, so that the situation that the similar characteristics of the same entity in the software product are inconsistent to the outside occurs.
Disclosure of Invention
The embodiment of the application provides a method and a device for expanding public service logic of a domain entity, which are used for solving the problems that in domain-driven design and development, the service logic has strong dispersity, repeated development is easily caused, and extra workload of developers is increased.
The method for expanding the public service logic of the domain entity provided by the embodiment of the application comprises the following steps:
determining an interface standard of a preset type; the type represents the public service logic of the entity, and the interface standard comprises type metadata information, a type metadata operation interface and an entity metadata type operation interface;
calling the type metadata operation interface to acquire type information;
and calling the entity metadata version operation interface according to the acquired version information, and determining a version corresponding to the version information added or removed from the entity to be operated.
In one example, calling the type metadata operation interface to obtain type information includes: calling the type metadata operation interface to acquire all type information in a type list; and determining the type information to be operated corresponding to the entity to be operated from all the type information.
In one example, according to the obtained type information, invoking the entity metadata type operation interface, and determining a type corresponding to the type information added or removed from the entity to be operated includes: calling a type adding method or a type removing method in the entity metadata type operation interface; transmitting the acquired layout information to a corresponding layout adding method or a corresponding layout removing method; and executing the operation of adding the edition or removing the edition from the entity to be operated.
In one example, the operation of adding a type or removing a type from the entity to be operated is executed, and the operation comprises the following steps: determining an attribute field corresponding to the acquired type information; adding the attribute field into the entity to be operated, or removing the attribute field from the entity to be operated.
In one example, the interface standard includes a type metadata operation interface configuration; calling the type metadata operation interface, including: and acquiring corresponding configuration information according to the configuration of the type metadata operation interface, and loading a program to call the type metadata operation interface.
In one example, the interface standard includes an entity metadata layout operation interface configuration; calling the entity metadata layout operation interface, including: and acquiring corresponding configuration information according to the configuration of the entity metadata layout operation interface, and loading a program to call the entity metadata layout operation interface.
In one example, the interface standard includes a type base interface; the method further comprises the following steps: and calling the type base interface to obtain the type attribute value corresponding to the entity to be operated.
In one example, the interface standard includes a type base interface; the method further comprises the following steps: and calling the version base interface, and setting the attribute value of the corresponding version to be operated in the entity to be operated according to the attribute name of the version to be operated.
In one example, the interface standard includes a type property interface; the method further comprises the following steps: and calling the version characteristic interface to realize the characteristic business logic operation of the corresponding version.
An apparatus for extending a public service logic of a domain entity provided in an embodiment of the present application includes:
the first determining module is used for determining the interface standard of a preset type; the type represents the public service logic of the entity, and the interface standard comprises type metadata information, a type metadata operation interface and an entity metadata type operation interface;
the acquisition module calls the type metadata operation interface to acquire type information;
and the second determining module calls the entity metadata version operation interface according to the acquired version information and determines to add or remove the version corresponding to the version information from the entity to be operated.
The method and the device for expanding the public service logic of the domain entity provided by the embodiment of the application at least have the following beneficial effects:
and presetting a plurality of versions according to the entity public service logic, and packaging the processing of the entity public service logic for the entity to call.
Therefore, the mapping relation between the entity metadata and the types can be used for marking which types are applied to the current entity on the domain entity metadata, and further, the public service logic provided by the types is automatically acquired in the running process, so that the energization of the domain entity is realized.
Moreover, through the application of a plurality of entities to the same type, the plurality of entities can be ensured to be consistent in the same business logic, and the association between the same type and the plurality of entities can be established, so that the plurality of entities can be managed together.
The method can expand the public service logic of the field entity, simplify the public service logic of the unified field entity, avoid or reduce the problem of repeated development, reduce the workload of a development designer, save the development time, and be beneficial to reducing the problems of modification omission, errors and the like while improving the development experience.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a method for extending a common service logic of a domain entity according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a device of a common service logic of an extended domain entity according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a flowchart of a method for extending a public service logic of a domain entity according to an embodiment of the present application, which specifically includes the following steps:
s101: and determining the interface standard of the preset version.
In the embodiment of the application, the server can determine the interface standard of the preset version. The preset type is set by a software development designer according to the public logic of the entity in advance, the content and the quantity of the preset type can be set according to the requirement, and the interface standard is the interface standard which is required to be followed by the entity and the type in the public logic expansion process.
Specifically, the interface standard includes type metadata information, a type metadata operation interface, and an entity metadata type operation interface.
The type metadata information comprises type metadata basic information and type metadata attribute information.
The layout metadata basic information is basic information for defining a layout, and includes 6 attributes: the layout type comprises a layout type identifier, a layout type code, a layout type name, a description, a layout type interface full name and a layout type realization full name. Wherein, the 'type identification' is used for uniquely identifying one type; the 'type code' represents the code of the type, and is the further division of the information with the same type mark; "type name" represents the name of the type; "description" means the common business logic provided by the layout; the 'full name of the type interface class' represents the full name of the type interface class; the 'type realization type full name' represents the realization type full name corresponding to the type interface and is used for reflecting the example of recording the type interface.
The type metadata attribute information is used for recording information related to the type attribute, and comprises 8 attributes: type attribute identification, type identification, attribute coding, attribute name, data type, length, whether filling is necessary or not, and default values. The 'type attribute identifier' is used for uniquely identifying one type attribute; the 'type identification' is used for uniquely identifying one type; the 'attribute coding' represents the coding of the type attribute, and is the further division of the information with the same attribute identification; "attribute name" represents the name of the type attribute; the data type represents a data type corresponding to the type attribute; "length" is an output storage length for describing the attribute of the character string type; "fill-necessary" is used to identify whether the type attribute must be filled, i.e. whether the corresponding field on the entity to which the type belongs must be filled; the "default value" represents a default value of the type attribute, that is, the default value of the corresponding attribute after the corresponding type is applied to the entity.
S102: and calling a type metadata operation interface to acquire type information.
In the embodiment of the application, after the entity to be operated and the corresponding entity metadata are established, the server can obtain the type information required by the entity to be operated by calling the type metadata operation interface. Wherein, the agent operation entity represents the entity needing to set the business logic.
The layout metadata operation interface is used for realizing the operation on the layout, and comprises two methods: the method comprises the steps of obtaining basic information of the type and obtaining attribute information of the type. The 'obtaining type basic information' is used for obtaining a type list corresponding to all types, and the 'obtaining type basic information' can return a list of type basic information of all types; the "obtaining type attribute information" is used for obtaining type attribute information of a type to be operated, and can return to a list of the type attribute information according to the input parameter of the type identifier.
In one embodiment, the server may obtain all the layout information in the preset layout list by calling the layout metadata operation interface. And the server can determine the type information to be operated from all the type information according to the input type identification. Wherein the layout information to be operated represents information of a layout to be applied to or removed from the entity.
In one embodiment, the interface standard further comprises a type metadata operation interface configuration used for recording a set of type metadata operation interfaces provided in the current system. The server can obtain corresponding configuration information according to the configuration of the type metadata operation interface and load a program so as to realize the calling of the type metadata operation interface.
S103: and calling an entity metadata version operation interface according to the acquired version information, and determining a version corresponding to the corresponding version information added or removed from the entity to be operated.
In the embodiment of the application, after determining the type information to be operated, the server may operate the corresponding relationship between the entity metadata and the type by calling the entity metadata type operation interface, so as to add or remove the corresponding type from the entity to be operated.
The entity metadata layout operation interface is used for realizing the operation of adding a layout or removing a layout to the entity metadata, and comprises two methods: "Add version" and "remove version". Wherein, the 'adding type' is used for applying the type to be operated to the entity metadata, and the 'removing type' is used for removing the type to be operated from the entity metadata.
In one embodiment, the operation of adding the version to the entity metadata by the server specifically includes the following steps:
firstly, calling a type adding method in an entity metadata type operation interface;
secondly, transmitting the pre-acquired type information to be operated (namely to be added) to a corresponding type adding method;
thirdly, an operation of adding a version from the entity to be operated is performed.
Specifically, the server may determine an attribute field corresponding to the type information to be added, and then the server may copy the attribute field of the type and add the copied attribute field to the entity metadata, and add a piece of type information to the entity metadata to establish an association relationship between the entity metadata and the type. Therefore, during the running of the software, the server can dynamically acquire the information of the corresponding version through the entity metadata.
In one embodiment, the operation of removing the version of the entity metadata by the server specifically comprises the following steps:
firstly, calling a type removing method in an entity metadata type operation interface;
secondly, transmitting the pre-acquired type information to be operated (namely to be removed) to a corresponding type removing method;
thirdly, an operation of removing the version from the entity to be operated is performed.
Specifically, the server may determine an attribute field corresponding to the type information to be removed, and then, the server may remove the same attribute field in the entity metadata according to the attribute field of the type, so as to cancel the association relationship between the entity metadata and the type.
In one embodiment, an entity metadata layout operation interface configuration is also included in the interface standard for recording the set of entity metadata layout operation interfaces provided in the current system. The server can obtain corresponding configuration information according to the configuration of the entity metadata layout operation interface, and loads a program to realize the calling of the entity metadata layout operation interface.
In one embodiment, a type-based interface is also included in the interface standard. The layout-based interface is used for defining common operations of all layouts, and comprises two methods: the method comprises the steps of loading entity type attribute values and setting entity type attribute values, wherein the two methods are used in the running process of all types.
The "loading entity type attribute value" is used for obtaining an attribute value list of type attributes included in the type of the entity application, and can load the mapping relationship between entity metadata and the type and return the corresponding key-value pair mapping of the attribute name and the attribute value. The "set entity type attribute value" is used to set the value of the corresponding type attribute on the entity, and can set the value of the corresponding attribute name according to the mapping between the input attribute name and the attribute value.
Therefore, the server can call an entity type attribute value loading method in the type base interface during the operation of the system to acquire the type attributes in the entity, and then set the corresponding values of the type attributes in the entity according to the input values by calling an entity type attribute value setting method.
In one embodiment, a type property interface may also be included in the interface standard. The layout characteristic interface is used for defining characteristic business logic of the layout, is the business logic specific to the layout, and corresponds to the layout base interface. During the operation of the system, the server can realize the characteristic operation in the type by calling the type characteristic interface, such as checking the related data in the entity.
In one embodiment, the version-based interface may be implemented by a version-based interface class, which is also inherited by the implementation classes of all version properties.
In the embodiment of the application, a plurality of versions are preset according to the entity public service logic, and the processing of the entity public service logic is encapsulated for the entity to call.
Therefore, the mapping relation between the entity metadata and the types can be used for marking which types are applied to the current entity on the domain entity metadata, and further, the public service logic provided by the types is automatically acquired in the running process, so that the energization of the domain entity is realized.
Moreover, through the application of a plurality of entities to the same type, the plurality of entities can be ensured to be consistent in the same business logic, and the association between the same type and the plurality of entities can be established, so that the plurality of entities can be managed together.
The method can actually avoid or reduce the problem of repeated development while improving the development experience, reduce the workload of a development designer, save the development time, and is favorable for reducing the problems of modification omission, errors and the like.
For ease of understanding, the present application will be described with an "expiration control" version as an example.
In the implementation scenario of the layout, three phases are included: prefabrication phase, development phase and operation phase. In the prefabrication stage, the server can determine the basic information and the attribute information of a preset 'validity period control' type. Wherein, the basic information is shown in table 1:
TABLE 1
| Attribute name | Value of |
| Layout mark | EffectiveControl |
| Plate type coding | EffectiveControl |
| Plate type name | Period of validity |
| Description of the invention | Validity period common service logic including validation and invalidation common operations |
| Full name of type interface class | com.erp.demo.IEffective |
| Full name of type interface realization class | com.erp.demo.EffectiveImpl |
The type interface type com.erp.demo.ieffective includes two common service logic operations of "effective" and "ineffective".
The attribute information is shown in table 2:
TABLE 2
In the development stage, after the server establishes the entity metadata of the bill of material, the server can add the validity period control type to a type list of the entity metadata of the bill of material through an entity metadata type operation interface. Therefore, the information of the 'validity period control' version is added in the version list of the bill of material entity metadata, and three fields of validity, effective date and expiration date are added in the entity attribute list.
In the operation stage, the entity can carry out corresponding effective or ineffective operation by calling the type interface type com.erp.demo.IEffective in the 'validity period control' type interface, thereby realizing the expansion of the entity bill of material public service logic operation.
Based on the same inventive concept, the method for extending the public service logic of the domain entity provided in the embodiment of the present application further provides a corresponding device for extending the public service logic of the domain entity, as shown in fig. 2.
Fig. 2 is a schematic structural diagram of a device for public service logic of an extended domain entity according to an embodiment of the present application, which specifically includes:
a first determining module 201, configured to determine an interface standard of a preset type; the type represents the public service logic of the entity, and the interface standard comprises type metadata information, a type metadata operation interface and an entity metadata type operation interface;
the obtaining module 202 calls the type metadata operation interface to obtain type information;
the second determining module 203 invokes the entity metadata version operation interface according to the acquired version information, and determines a version corresponding to the version information to be added or removed from the entity to be operated.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for extending a common service logic of a domain entity, comprising:
determining an interface standard of a preset type; the type represents the public service logic of the entity, and the interface standard comprises type metadata information, a type metadata operation interface and an entity metadata type operation interface;
calling the type metadata operation interface to acquire type information;
and calling the entity metadata version operation interface according to the acquired version information, and determining a version corresponding to the version information added or removed from the entity to be operated.
2. The method of claim 1, wherein invoking the type metadata manipulation interface to obtain type information comprises:
calling the type metadata operation interface to acquire all type information in a type list;
and determining the type information to be operated corresponding to the entity to be operated from all the type information.
3. The method according to claim 1, wherein calling the entity metadata layout operation interface according to the acquired layout information, and determining a layout corresponding to the layout information to be added or removed from the entity to be operated, comprises:
calling a type adding method or a type removing method in the entity metadata type operation interface;
transmitting the acquired layout information to a corresponding layout adding method or a corresponding layout removing method;
and executing the operation of adding the edition or removing the edition from the entity to be operated.
4. The method according to claim 3, wherein the operation of adding a type or removing a type from the entity to be operated is performed, and comprises:
determining an attribute field corresponding to the acquired type information;
adding the attribute field into the entity to be operated, or removing the attribute field from the entity to be operated.
5. The method of claim 1, wherein the interface standard comprises a type metadata manipulation interface configuration;
calling the type metadata operation interface, including:
and acquiring corresponding configuration information according to the configuration of the type metadata operation interface, and loading a program to call the type metadata operation interface.
6. The method of claim 1, wherein the interface standard comprises an entity metadata layout operation interface configuration;
calling the entity metadata layout operation interface, including:
and acquiring corresponding configuration information according to the configuration of the entity metadata layout operation interface, and loading a program to call the entity metadata layout operation interface.
7. The method of claim 1, wherein the interface standard comprises a version-based interface; the method further comprises the following steps:
and calling the type base interface to obtain the type attribute value corresponding to the entity to be operated.
8. The method of claim 1, wherein the interface standard comprises a version-based interface; the method further comprises the following steps:
and calling the version base interface, and setting the attribute value of the corresponding version to be operated in the entity to be operated according to the attribute name of the version to be operated.
9. The method of claim 1, wherein the interface standard comprises a type property interface; the method further comprises the following steps:
and calling the version characteristic interface to realize the characteristic business logic operation of the corresponding version.
10. An apparatus for extending a common service logic of a domain entity, comprising:
the first determining module is used for determining the interface standard of a preset type; the type represents the public service logic of the entity, and the interface standard comprises type metadata information, a type metadata operation interface and an entity metadata type operation interface;
the acquisition module calls the type metadata operation interface to acquire type information;
and the second determining module calls the entity metadata version operation interface according to the acquired version information and determines to add or remove the version corresponding to the version information from the entity to be operated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010603404.5A CN111984240A (en) | 2020-06-29 | 2020-06-29 | Method and device for expanding public service logic of domain entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010603404.5A CN111984240A (en) | 2020-06-29 | 2020-06-29 | Method and device for expanding public service logic of domain entity |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111984240A true CN111984240A (en) | 2020-11-24 |
Family
ID=73441918
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010603404.5A Pending CN111984240A (en) | 2020-06-29 | 2020-06-29 | Method and device for expanding public service logic of domain entity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111984240A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106301885A (en) * | 2016-07-18 | 2017-01-04 | 乐视控股（北京）有限公司 | The method and system of uniform traffic management |
| CN106412072A (en) * | 2016-10-08 | 2017-02-15 | 腾讯科技（深圳）有限公司 | Service processing method and apparatus |
| CN107622055A (en) * | 2016-07-13 | 2018-01-23 | 航天科工智慧产业发展有限公司 | A kind of quick method for realizing data, services issue |
| CN109947422A (en) * | 2019-03-14 | 2019-06-28 | 浪潮通用软件有限公司 | A kind of Business Entity realization method and system based on Domain Driven Design |
| CN110058853A (en) * | 2019-04-22 | 2019-07-26 | 武汉众邦银行股份有限公司 | A kind of API procedure method controlled based on workflow and permission |
| CN110781165A (en) * | 2019-10-10 | 2020-02-11 | 支付宝(杭州)信息技术有限公司 | Method, device and equipment for processing service data |
-
2020
- 2020-06-29 CN CN202010603404.5A patent/CN111984240A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107622055A (en) * | 2016-07-13 | 2018-01-23 | 航天科工智慧产业发展有限公司 | A kind of quick method for realizing data, services issue |
| CN106301885A (en) * | 2016-07-18 | 2017-01-04 | 乐视控股（北京）有限公司 | The method and system of uniform traffic management |
| CN106412072A (en) * | 2016-10-08 | 2017-02-15 | 腾讯科技（深圳）有限公司 | Service processing method and apparatus |
| CN109947422A (en) * | 2019-03-14 | 2019-06-28 | 浪潮通用软件有限公司 | A kind of Business Entity realization method and system based on Domain Driven Design |
| CN110058853A (en) * | 2019-04-22 | 2019-07-26 | 武汉众邦银行股份有限公司 | A kind of API procedure method controlled based on workflow and permission |
| CN110781165A (en) * | 2019-10-10 | 2020-02-11 | 支付宝(杭州)信息技术有限公司 | Method, device and equipment for processing service data |
Non-Patent Citations (1)
| Title |
|---|
| 四叶猫: "蜗牛一般的UAP开发(二)元数据", 《HTTPS://BLOG.CSDN.NET/QQ_42994789/ARTICLE/DETAILS/106079833》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109840429B (en) | Intelligent contract deployment and calling method and device | |
| US10481903B2 (en) | On-demand database service system, method, and computer program product for validating a developed application | |
| CN111104392B (en) | Database migration method and device, electronic equipment and storage medium | |
| JP5162094B2 (en) | Method and apparatus for metadata-driven business logic processing | |
| US20060026585A1 (en) | Automatic upgrade of pluggable components | |
| JP2005078649A (en) | Branding framework | |
| CN115993966B (en) | Application development system and method | |
| CN113867719A (en) | Third-party library function disassembling and calling method and system for software platform | |
| CN113569257B (en) | User authority management method and device in gray level release | |
| CN109840078B (en) | Method and device for collaboratively editing hierarchical metadata | |
| CN112363997A (en) | Data version management method, device and storage medium | |
| US20090138621A1 (en) | System and method for delegating a dependent business object | |
| CN111984240A (en) | Method and device for expanding public service logic of domain entity | |
| CN116644122A (en) | Data transaction processing method, device, computer equipment and storage medium | |
| US20090144752A1 (en) | Unmanaged-to-managed aggregation | |
| CN114238352A (en) | Micro-service processing method and related device | |
| US7225435B2 (en) | Method and system for eliminating redundant execution sequences that appear in workloads during workload simulation on an e-business application server | |
| CN113220762A (en) | Method, device, processor and storage medium for realizing general record processing of key service field change in big data application | |
| CN112749152A (en) | Data migration method and device of intelligent contract and storage medium | |
| CN112817931A (en) | Method and device for generating incremental version file | |
| CN111652580A (en) | Method and device for processing data of nodes | |
| CN111159198B (en) | Parameter transaction processing method and device, computer equipment and readable storage medium | |
| CN112965706B (en) | Description method, device and medium of data types | |
| CN116048498B (en) | Component library architecture based on multiple versions | |
| CN113254064B (en) | API (application program interface) management method and system of block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201124 |
|
| RJ01 | Rejection of invention patent application after publication |