CN113849189A - Project hot deployment method and device - Google Patents
Project hot deployment method and device Download PDFInfo
- Publication number
- CN113849189A CN113849189A CN202111141795.4A CN202111141795A CN113849189A CN 113849189 A CN113849189 A CN 113849189A CN 202111141795 A CN202111141795 A CN 202111141795A CN 113849189 A CN113849189 A CN 113849189A
- Authority
- CN
- China
- Prior art keywords
- project
- host
- loading
- target
- container
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a project hot deployment method and a device, when the method and the device are used for project deployment, different user-defined class loaders and different sub-containers are respectively created for different projects to be deployed, project file packages of the different projects to be deployed are loaded by using the different user-defined class loaders, and resources (such as components) in the file packages of the different projects to be deployed are loaded by using the different sub-containers, so that project instances of the different projects to be deployed are isolated from each other, the mutual influence among the different projects is reduced, and only business related codes are loaded (the project file packages and data access layer components only relate to the business related codes), so that the projects are automatically and dynamically deployed under the condition of low memory consumption, and the cost and the complexity of the project deployment are reduced.
Description
Technical Field
The application belongs to the field of project development and deployment, and particularly relates to a project hot deployment method and device.
Background
The automatic development platform can generate java codes according to an interface operation mode, general java items need to be compiled and packaged, and a jar file or a war file is generated. And the interface service can be provided to the outside only by manual deployment through the web container.
The new automation platform can generate a large amount of codes of java projects, the codes need a lot of workload when being deployed on a server, a specially-assigned person is correspondingly needed to perform manual deployment operation on the generated codes and maintain and solve a series of problems in deployment, the efficiency is low, the manual workload is large, and therefore a scheme for automatically and dynamically deploying projects, which can replace manual operation, is urgently needed.
Disclosure of Invention
In view of the above, the present application provides a project hot deployment method and apparatus for automatically and dynamically deploying projects without manual operations and with less memory consumption, so as to reduce the cost and complexity of deploying projects.
The specific technical scheme is as follows:
a project hot deployment method, comprising:
loading a project file package of a target project to be deployed through the created self-defined class loader;
loading the resources contained in the project file package through the created child container; the child container inherits resources in a parent container of a host item of the target item, can share common resources, and different items to be deployed respectively correspond to different custom class loaders and different child containers;
loading data access layer components to the host project;
registering an interface address mapping of a service interface of a predetermined page service into a parent container of the host project, so as to load the target project into the host project and provide the predetermined page service.
Optionally, the loading, by the created custom class loader, the project file package of the target project to be deployed includes:
aiming at a target project to be deployed, a self-defined class loader is established for the target project;
and loading a jar file package or a war file package of the target item by utilizing the created self-defined class loader.
Optionally, the loading the resources included in the project file package through the created child container includes:
scanning components in the project portfolio using a scanner and registering the scanned components in a parent container of the host project;
creating a child container, and loading the components contained in the project portfolio using the created child container.
Optionally, the loading the data access layer component to the host project includes:
scanning data access layer components using a scanner, registering the scanned data access layer components in a parent container of the host item; before registration, the cached historical registration information of the data access layer component is cleared;
the data access layer components are loaded.
Optionally, the mapping an interface address of a service interface of a predetermined page service is registered in a parent container of the host project so as to load the target project into the host project and provide the predetermined page service, where the mapping includes:
mapping and registering a uniform resource locator url of a hypertext transfer protocol (http) interface into a parent container of the host project so as to load the target project into the host project and provide an http service;
wherein the cached historical registration information of the url mapping is cleared prior to registration.
Optionally, the method further includes:
and when the target item needs to be unloaded, unloading the target item and the resources occupied by the target item by deleting the class loader and the sub-container corresponding to the target item.
A project hot deployment device, comprising:
the first loading processing module is used for loading a project file package of a target project to be deployed through the created self-defined class loader;
the second loading processing module is used for loading the resources contained in the project file package through the created child container; the child container inherits resources in a parent container of a host item of the target item, can share common resources, and different items to be deployed respectively correspond to different custom class loaders and different child containers;
the third loading processing module is used for loading the data access layer component to the host project;
and the interface address mapping registration module is used for registering the interface address mapping of the service interface of the predetermined page service into the parent container of the host project so as to load the target project into the host project and provide the predetermined page service.
Optionally, the first load processing module is specifically configured to:
aiming at a target project to be deployed, a self-defined class loader is established for the target project;
loading a jar file package or a war file package of the target item by utilizing the created self-defined class loader;
the second load processing module is specifically configured to:
scanning components in the project portfolio using a scanner and registering the scanned components in a parent container of the host project;
creating a child container, and loading the components contained in the project portfolio using the created child container.
Optionally, the third load processing module is specifically configured to:
scanning data access layer components using a scanner, registering the scanned data access layer components in a parent container of the host item; before registration, the cached historical registration information of the data access layer component is cleared;
loading a data access layer component;
the interface address mapping registration module is specifically configured to:
registering url mapping of an http interface into a parent container of the host project so as to load the target project into the host project and provide http service;
wherein the cached historical registration information of the url mapping is cleared prior to registration.
Optionally, the apparatus further includes:
and the unloading processing module is used for unloading the target item and the resources occupied by the target item by deleting the class loader and the sub-container corresponding to the target item when the target item needs to be unloaded.
According to the scheme, when the project is deployed, different custom class loaders and different sub-containers are respectively created for different projects to be deployed, project file packages of the different projects to be deployed are loaded by using the different custom class loaders, and resources (such as components) in the file packages of the different projects to be deployed are loaded by using the different sub-containers, so that project instances of the different projects to be deployed are isolated from each other, the mutual influence among the different projects is reduced, and only business related codes are loaded (the project file packages and the data access layer components only relate to the business related codes), so that the projects are automatically and dynamically deployed under the condition of low memory consumption, and the cost and the complexity of the project deployment are reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a schematic flow chart of a project heat deployment method provided herein;
FIG. 2 is a schematic illustration of a data access registration and a url map registration with a parent container of a host project as provided herein;
FIG. 3 is an application example of the project heat deployment method provided herein;
FIG. 4 is another schematic flow diagram of a project hot deployment method provided herein;
fig. 5 is a schematic structural diagram of a project thermal deployment apparatus provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part 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.
The deployment and release of general projects need manual compiling and packaging, and need to use scripts or operating system commands to start the deployment of web application projects, and the deployment is performed through a web container to realize external interface service provision. In order to implement an automated deployment scheme that replaces manual operation, there is currently a technology based on Open Service Gateway Initiative (osgi) that can perform automated hot deployment of a project, but the technology needs to hot load components including a web container, resulting in relatively more consumed server memory.
In order to solve the problem, the project is automatically and dynamically deployed and published without manual operation and with less memory consumption, and a predetermined page service (such as an http service) is provided, so that the cost and the complexity of the project deployment are reduced, the application discloses a project hot deployment method and a project hot deployment device.
The processing flow of the project heat deployment method disclosed by the application is shown in fig. 1, and specifically comprises the following steps:
and step 101, loading a project file package of a target project to be deployed through the created custom class loader.
The project file package can be, but is not limited to, a jar file package or a war file package obtained by compiling and packaging project codes (e.g., java codes).
For a target project to be deployed, a custom class loader is created for the target project, and a project file package, such as a jar file package, of the target project to be deployed is loaded by using the custom class loader.
Wherein, the created custom class loader inherits the application class loader of the host project (or host application).
And for different projects to be deployed, different custom class loaders are respectively created for the different projects to be deployed, and project file packages of the different projects to be deployed are respectively loaded through the different custom class loaders. Different self-defined class loaders are used, so that different projects are isolated from each other, and in addition, each self-defined class loader respectively inherits the application class loader of the host project, so that common resources do not need to be repeatedly loaded.
And 102, loading the resources contained in the project file package through the created child container.
On the basis of loading a project file package of a target project to be deployed through a self-defined class loader, a scanner is used for scanning components in the project file package of the target project, the scanned components are registered in a parent container of a host project, a child container is created for the target project to be deployed, and the created child container is used for loading the resources, namely, each component in the project file package of the target project is loaded.
The scanner is embodied as a scanning component in the parent container of the host item.
The child containers inherit resources in the parent container of the host item and are able to share common resources, such as may include, but are not limited to, common data source information. Different items to be deployed correspond to different custom class loaders and different sub-containers respectively.
Illustratively, referring to fig. 2 in combination, after loading a jar package of an item to be deployed by using a custom class loader, a scanner in a parent container of a host item is used to scan components in the jar package, the scanned components are registered in the parent container of the host item, and a spring child container is created to load the resources (components in the jar package).
And 103, loading the data access layer component to the host project.
For the dynamically loaded target project to be deployed, the data access layer components are not loaded by the system, so the data access layer components need to be scanned and loaded.
In particular, a scanner (a scanning component in the parent container of the host item) may be used to scan the data access layer components, register the scanned data access layer components into the parent container of the host item, and load the data access layer components.
Wherein, prior to registration, the history registration information of the cached data access layer component is cleared.
Illustratively, the data access layer components may include mybatisps components that delete the registration information for the components that were cached prior to scanning the data access layer components and registering them in the parent container of the host project.
And step 104, registering the interface address mapping of the service interface of the predetermined page service into a parent container of the host project so as to load the target project into the host project and provide the predetermined page service.
The interface address mapping of the service interface of the predetermined page service is not registered in the system, and therefore, the interface address mapping of the service interface of the predetermined page service needs to be registered and updated to the system together, and the cached history registration information of the interface address mapping needs to be cleared before registration and update.
The predetermined page service may be, but is not limited to, an http (HyperText Transfer Protocol) service. Taking http service as an example, the url mapping of the http interface may be registered in a parent container of the host project (and the registration information of the url mapping that has been cached before registration is cleared), so as to load the target project to be deployed into the host project and provide the http service, thereby implementing automatic and dynamic hot deployment of the target project to be deployed.
Because the project file package and the data access layer component only relate to the service related codes, in the project hot deployment process, on the basis of carrying out related loader (such as application class loader) and resource inheritance, the project hot deployment method can finish the automatic and dynamic deployment of the project by establishing the corresponding custom class loader and the spring sub-container to only load the service related codes, does not deploy through the web container, correspondingly does not need to carry out hot loading on the component containing the web container, and reduces the occupation of the memory.
Based on the project hot deployment method disclosed in the embodiment of the present application, referring to the example provided in fig. 3, in practical application, a project release directory may be scanned regularly, and when a project to be deployed is scanned, a jar file package of the project is loaded by using a custom class loader, a component in the jar file package is loaded by using a created spring child container, and a series of processes such as registration of a data access layer component and url mapping are performed, so as to implement automatic and dynamic deployment of the project.
According to the scheme, when the project deployment is carried out, different custom class loaders and different sub-containers are respectively created for different projects to be deployed, project file packages of the different projects to be deployed are loaded by using the different custom class loaders, and resources (such as components) in the file packages of the different projects to be deployed are loaded by using the different sub-containers, so that project instances of the different projects to be deployed are isolated from each other, the mutual influence among the different projects is reduced, and by only loading service related codes (the project file packages and the data access layer components only relate to the service related codes), the projects are automatically and dynamically deployed under the condition of low memory consumption, so that the cost and the complexity of the project deployment are reduced.
In an embodiment, referring to the processing flow of the project heat deployment method provided in fig. 4, the method of the present application may further include:
and 105, when the target item needs to be unloaded, unloading the target item and the resources occupied by the target item by deleting the class loader and the sub-container corresponding to the target item.
Specifically, when a deployed project needs to be unloaded, the class loader and the sub-container, such as a spring sub-container, corresponding to the project are directly deleted, and the unloading of the project and occupied resources, such as memory resources, of the project can be realized. Because the deployed instances of different projects are isolated from each other, the unloading of one project does not result in the influence on other projects.
Corresponding to the above method, an embodiment of the present application further discloses a memory management device, as shown in fig. 5, the memory management device includes:
a first loading processing module 501, configured to load a project file package of a target project to be deployed through a created custom class loader;
a second loading processing module 502, configured to load the resources included in the project file package through the created child container; the child container inherits resources in a parent container of a host item of the target item, can share common resources, and different items to be deployed respectively correspond to different custom class loaders and different child containers;
a third loading processing module 503, configured to load the data access layer component to the host project;
an interface address mapping registration module 504, configured to register an interface address mapping of a service interface of a predetermined page service into a parent container of a host project, so as to load the target project into the host project and provide the predetermined page service.
In an embodiment, the first load processing module 501 is specifically configured to:
aiming at a target project to be deployed, a self-defined class loader is established for the target project;
loading a jar file package or a war file package of the target item by utilizing the created class loader;
the second load processing module 502 is specifically configured to:
scanning components in the project file package by using a scanner, and registering the scanned components in a parent container of a host project;
creating a child container, and loading the components contained in the project portfolio using the created child container.
In an embodiment, the third load processing module 503 is specifically configured to:
scanning the data access layer components by using a scanner, and registering the scanned data access layer components into a parent container of a host project; before registration, the history registration information of the cached data access layer component is cleared;
loading a data access layer component;
the interface address mapping registration module 504 is specifically configured to:
mapping and registering a uniform resource locator url of a hypertext transfer protocol (http) interface into a parent container of a host project so as to load the target project into the host project and provide an http service;
wherein the cached historical registration information of the url mapping is cleared prior to registration.
In an embodiment, the apparatus further includes:
and the unloading processing module is used for unloading the target item and the resources occupied by the target item by deleting the class loader and the sub-container corresponding to the target item when the target item needs to be unloaded.
The thermal deployment device disclosed in the embodiments of the present application is relatively simple in description since it corresponds to the thermal deployment method disclosed in the above method embodiments, and for the relevant similarities, please refer to the description of the corresponding method embodiments above, and detailed description is omitted here.
In summary, according to the project hot deployment method and apparatus disclosed in the present application, different custom class loaders and child containers are created for different projects to be deployed, the deployed projects are managed and isolated, the created child containers and the containers (i.e., parent containers) of the host projects are integrated by inheriting the class loaders and resources of the host projects, registration and update of http interface url mapping are performed by dynamic scan loading of data access layer components, so that the system does not need manual operation, and projects can be automatically and dynamically deployed and published under the condition of low memory consumption, and http service is provided, thereby reducing the cost and complexity of project deployment.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other.
For convenience of description, the above system or apparatus is described as being divided into various modules or units by function, respectively. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present application.
Finally, it is further noted that, herein, relational terms such as first, second, third, fourth, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (10)
1. A project hot deployment method, comprising:
loading a project file package of a target project to be deployed through the created self-defined class loader;
loading the resources contained in the project file package through the created child container; the child container inherits resources in a parent container of a host item of the target item, can share common resources, and different items to be deployed respectively correspond to different custom class loaders and different child containers;
loading data access layer components to the host project;
registering an interface address mapping of a service interface of a predetermined page service into a parent container of the host project, so as to load the target project into the host project and provide the predetermined page service.
2. The method of claim 1, wherein loading the project package of the target project to be deployed by the created custom class loader comprises:
aiming at a target project to be deployed, a self-defined class loader is established for the target project;
and loading a jar file package or a war file package of the target item by utilizing the created self-defined class loader.
3. The method of claim 1, wherein the loading the resources contained in the project portfolio through the created child containers comprises:
scanning components in the project portfolio using a scanner and registering the scanned components in a parent container of the host project;
creating a child container, and loading the components contained in the project portfolio using the created child container.
4. The method of claim 1, wherein loading data access layer components into the host project comprises:
scanning data access layer components using a scanner, registering the scanned data access layer components in a parent container of the host item; before registration, the cached historical registration information of the data access layer component is cleared;
the data access layer components are loaded.
5. The method of claim 1, wherein registering an interface address mapping of a service interface of a predetermined page service into a parent container of the host project to facilitate loading the target project into the host project and providing the predetermined page service comprises:
mapping and registering a uniform resource locator url of a hypertext transfer protocol (http) interface into a parent container of the host project so as to load the target project into the host project and provide an http service;
wherein the cached historical registration information of the url mapping is cleared prior to registration.
6. The method of any one of claims 1-5, further comprising:
and when the target item needs to be unloaded, unloading the target item and the resources occupied by the target item by deleting the class loader and the sub-container corresponding to the target item.
7. A project hot deployment device, comprising:
the first loading processing module is used for loading a project file package of a target project to be deployed through the created self-defined class loader;
the second loading processing module is used for loading the resources contained in the project file package through the created child container; the child container inherits resources in a parent container of a host item of the target item, can share common resources, and different items to be deployed respectively correspond to different custom class loaders and different child containers;
the third loading processing module is used for loading the data access layer component to the host project;
and the interface address mapping registration module is used for registering the interface address mapping of the service interface of the predetermined page service into the parent container of the host project so as to load the target project into the host project and provide the predetermined page service.
8. The apparatus of claim 7, wherein the first load processing module is specifically configured to:
aiming at a target project to be deployed, a self-defined class loader is established for the target project;
loading a jar file package or a war file package of the target item by utilizing the created self-defined class loader;
the second load processing module is specifically configured to:
scanning components in the project portfolio using a scanner and registering the scanned components in a parent container of the host project;
creating a child container, and loading the components contained in the project portfolio using the created child container.
9. The apparatus according to claim 7, wherein the third load processing module is specifically configured to:
scanning data access layer components using a scanner, registering the scanned data access layer components in a parent container of the host item; before registration, the cached historical registration information of the data access layer component is cleared;
loading a data access layer component;
the interface address mapping registration module is specifically configured to:
registering url mapping of an http interface into a parent container of the host project so as to load the target project into the host project and provide http service;
wherein the cached historical registration information of the url mapping is cleared prior to registration.
10. The apparatus of claim 7, further comprising:
and the unloading processing module is used for unloading the target item and the resources occupied by the target item by deleting the class loader and the sub-container corresponding to the target item when the target item needs to be unloaded.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111141795.4A CN113849189A (en) | 2021-09-28 | 2021-09-28 | Project hot deployment method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111141795.4A CN113849189A (en) | 2021-09-28 | 2021-09-28 | Project hot deployment method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113849189A true CN113849189A (en) | 2021-12-28 |
Family
ID=78980778
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111141795.4A Pending CN113849189A (en) | 2021-09-28 | 2021-09-28 | Project hot deployment method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113849189A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114443169A (en) * | 2022-01-28 | 2022-05-06 | 中国民生银行股份有限公司 | Method and device for realizing technical component platformization |
| CN115048313A (en) * | 2022-06-30 | 2022-09-13 | 中国电信股份有限公司 | Automatic testing method and device, computer readable storage medium and electronic equipment |
-
2021
- 2021-09-28 CN CN202111141795.4A patent/CN113849189A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114443169A (en) * | 2022-01-28 | 2022-05-06 | 中国民生银行股份有限公司 | Method and device for realizing technical component platformization |
| CN115048313A (en) * | 2022-06-30 | 2022-09-13 | 中国电信股份有限公司 | Automatic testing method and device, computer readable storage medium and electronic equipment |
| CN115048313B (en) * | 2022-06-30 | 2023-12-08 | 中国电信股份有限公司 | Automatic test method and device, computer readable storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113849189A (en) | Project hot deployment method and device | |
| Spiess et al. | SOA-based integration of the internet of things in enterprise services | |
| US6023579A (en) | Computer-implemented method for generating distributed object interfaces from metadata | |
| CN111596969A (en) | Software architecture method based on microkernel plus plug-in | |
| CN112822272B (en) | Micro-service gray level release method and device, computer equipment and storage medium | |
| CN105389186A (en) | Hot deployment method and system for Java application | |
| CN103218220A (en) | Dynamic pluggable component based-Internet of things middleware system | |
| CN103064663A (en) | Browser plug-in generating, issuing, loading and updating method and system | |
| CN109446648B (en) | Simulation service establishing method and device | |
| CN114064213B (en) | Quick arranging service method and system based on Kubernets container environment | |
| CN111651169B (en) | Block chain intelligent contract operation method and system based on web container | |
| CN104731622A (en) | Application program loading method and device and mobile terminal | |
| CN112579049A (en) | Customized software productization management method and device based on cloud platform | |
| CN102843342A (en) | Method and system for dynamically upgrading resource | |
| CN117707543A (en) | Application installation package manufacturing and installation method, computing device and storage medium | |
| CN101719069A (en) | Method and device of Web servitization of Java system | |
| CN108694048B (en) | Method for realizing batch publishing service | |
| CN114553703B (en) | Deployment method, device, equipment and storage medium of industrial equipment control strategy | |
| CN115827105A (en) | Micro front end architecture based method for dynamically loading main and sub applications | |
| US8260782B2 (en) | Data element categorization in a service-oriented architecture | |
| CN115421730A (en) | Method for dynamically loading unlimited-format static resource file in page | |
| US20180341475A1 (en) | Just In Time Deployment with Package Managers | |
| CN110968335A (en) | Component system for overall resource management of power business system | |
| CN111400054B (en) | Network plug-in calling method and device, computer storage medium and electronic equipment | |
| CN115344361A (en) | Management method and management system of computing nodes |
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 |