CN116049166A - Method and device for managing component data sources, storage medium and computer equipment - Google Patents

Method and device for managing component data sources, storage medium and computer equipment Download PDF

Info

Publication number
CN116049166A
CN116049166A CN202211341068.7A CN202211341068A CN116049166A CN 116049166 A CN116049166 A CN 116049166A CN 202211341068 A CN202211341068 A CN 202211341068A CN 116049166 A CN116049166 A CN 116049166A
Authority
CN
China
Prior art keywords
component
data source
data
configuration
determining
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
Application number
CN202211341068.7A
Other languages
Chinese (zh)
Inventor
毕伟
郭华
蔡宏伟
冯锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yuanguang Software Co Ltd
Original Assignee
Yuanguang Software Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Yuanguang Software Co Ltd filed Critical Yuanguang Software Co Ltd
Priority to CN202211341068.7A priority Critical patent/CN116049166A/en
Publication of CN116049166A publication Critical patent/CN116049166A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/211Schema design and management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/36Software reuse

Abstract

The embodiment of the application discloses a management method and device of a component data source, a storage medium and computer equipment, and relates to the field of component management. The method comprises the following steps: determining a plurality of components referenced by the application; configuring, for each component, a domain name of the component; determining a corresponding data source set according to the domain name; selecting one data source from the data source set to be allocated to the component; generating a component data source configuration file in a configuration center according to the field name and the data source identifier of each component; running an application in a sandbox; when an application program calls a component, determining a data source of the called component configuration according to a component data source configuration file; and executing data operation in the configured data sources through the called components, and isolating the data sources of all the components.

Description

Method and device for managing component data sources, storage medium and computer equipment
Technical Field
The present invention relates to the field of component management, and in particular, to a method and apparatus for managing component data sources, a storage medium, and a computer device.
Background
In order to improve code reusability, more and more applications are developed based on component modes. When an application program runs, a plurality of components in the component library can be used for realizing corresponding functions, and the components in the component library can be used by a plurality of different application programs. In the prior art, each component referenced by an application program can read data from and write data into a database of the application program during the operation process.
Disclosure of Invention
The embodiment of the application provides a management method, a device, a storage medium and computer equipment for component data sources, which can solve the problem that the data sources of components referenced by application programs of components in the prior art cannot be isolated from each other. The technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a method for managing component data sources, where the method includes:
determining a plurality of components referenced by the application;
for each component, configuring a domain name of the component;
determining a corresponding data source set according to the domain name;
selecting one data source from the set of data sources to be allocated to a component;
generating a component data source configuration file in a configuration center according to the field name and the data source identifier of each component;
running the application in a sandbox;
when the application program calls a component, determining a data source of the called component configuration according to the component data source configuration file;
and executing data operation in the configured data source through the called component.
In a second aspect, an embodiment of the present application provides a management apparatus for a component data source, where the apparatus includes:
a determining unit configured to determine a plurality of components referenced by the application program;
a configuration unit configured to configure, for each component, a domain name of the component;
the determining unit is further used for determining a corresponding data source set according to the domain name;
a selection unit for selecting one data source from the set of data sources to be allocated to a component;
the generating unit is used for generating a component data source configuration file in the configuration center according to the domain name and the data source identifier of each component;
the operation unit is used for operating the application program in the sandbox;
the determining unit is further used for determining a data source of the called component configuration according to the component data source configuration file when the application program calls the component;
and the execution unit is used for executing data operation in the configured data source through the called component.
In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-described method steps.
In a fourth aspect, embodiments of the present application provide a computer device, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.
The technical scheme provided by some embodiments of the present application has the beneficial effects that at least includes:
the method comprises the steps that domain names are respectively configured for all components referenced by an application program, independent data sources are respectively configured for each component according to the domain names, then component data source configuration information is generated according to the configuration, and when the application program operates and invokes the components, data operation is executed in the respective data sources of the components.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a network architecture provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for managing component data sources according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a configuration page of a domain name provided by an embodiment of the present application;
FIG. 4 is a schematic diagram of a data source configuration page provided by an embodiment of the present application;
FIG. 5 is a schematic diagram of an application deployment configuration page provided by an embodiment of the present application;
FIG. 6 is a schematic structural diagram of a management device for component data sources provided in the present application;
fig. 7 is a schematic structural diagram of a computer device provided in the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings.
It should be noted that, the method for managing component data sources provided in the present application is generally executed by a computer device, and accordingly, the device for managing component data sources is generally disposed in the computer device.
Fig. 1 illustrates an exemplary system architecture of a component data source management method or component data source management apparatus that may be applied to the present application.
As shown in fig. 1, the system architecture may include: a computer device 101 and a server 102. Communication between the computer device 101 and the server 102 may be through a network that is used as a medium to provide communication links between the various elements described above. The network may include various types of wired or wireless communication links, such as: the wired communication link includes an optical fiber, a twisted pair wire, a coaxial cable, or the like, and the WIreless communication link includes a bluetooth communication link, a WIreless-FIdelity (Wi-Fi) communication link, a microwave communication link, or the like.
Wherein, an application program is deployed in the computer device 101, the application program runs in the sandbox, the application program calls one or more components in the component library to realize corresponding functions, a configuration center is deployed in the server 102, and based on the component data source configuration information generated by the configuration center, each component is controlled to execute data operation in a corresponding data source.
The computer device 101 and the server 102 may be hardware or software. When the computer device 101 and the server 102 are hardware, they may be implemented as a distributed server cluster formed by a plurality of servers, or as a single server. When the computer device 101 and the server 102 are software, they may be implemented as a plurality of software or software modules (for example, to provide distributed services), or may be implemented as a single software or software module, which is not specifically limited herein.
Various communication client applications may be installed on the computer device of the present application, such as: video recording applications, video playing applications, voice interaction applications, search class applications, instant messaging tools, mailbox clients, social platform software, and the like.
The computer device may be hardware or software. When the computer device is hardware, it may be a variety of computer devices with a display screen including, but not limited to, smartphones, tablet computers, laptop and desktop computers, and the like. When the computer device is software, the computer device may be installed in the above-listed computer device. Which may be implemented as multiple software or software modules (e.g., to provide distributed services), or as a single software or software module, without limitation.
When the computer equipment is hardware, a display device and a camera can be arranged on the computer equipment, the display device can be various equipment capable of realizing the display function, and the camera is used for collecting video streams; for example: the display device may be a cathode ray tube display (cathode ray tube display, CR), a light-emitting diode display (light-emitting diode display, LED), an electronic ink screen, a liquid crystal display (liquid crystal display, LCD), a plasma display panel (plasma display panel, PDP), or the like. A user may utilize a display device on a computer device to view displayed text, pictures, video, etc.
It should be understood that the number of computer devices, networks, and servers in fig. 1 are illustrative only. Any number of computer devices, networks, and servers may be used as desired for implementation.
The method for managing component data sources according to the embodiment of the present application will be described in detail with reference to fig. 2. The management device of the component data source in the embodiment of the present application may be a computer device shown in fig. 1.
Referring to fig. 2, a flowchart of a method for managing component data sources is provided in an embodiment of the present application. As shown in fig. 2, the method according to the embodiment of the present application may include the following steps:
s201, determining a plurality of components referenced by the application program.
The application program is developed in a component mode, a plurality of components referenced by the application program are determined according to a development document of the application program, and development information of the application program is recorded in the development document, wherein the development document comprises but is not limited to: developer, component identification, data type, version update information, function description, etc., the component identification being used to uniquely identify the identity of the component.
S202, for each component, configuring the domain name of the component.
The computer device displays a configuration page through the display unit, a user executes configuration operation on the configuration page through the input unit, so as to realize configuration of field names of all components, the input unit can be a mouse, a keyboard or a touch screen, and the field names comprise: the field values of the fixed identification are fixed and are used for identifying the information as a field name, the product domain identification represents the identity of the product domain, the product line identification represents the identity of the product line, and the field values of the field codes are generally represented by character strings. The component may be a front-end component, a back-end component, or a composite component.
For example, referring to the configuration page shown in fig. 3, a component icon of each component referenced by the application program is displayed on a display unit of the computer device, and when a triggering operation of the component icon is detected, the configuration page shown in fig. 3 is displayed, and the user configures the fields and field values of the components based on the configuration page, where the fields include: the component title, component name, component hierarchy, component description, and component domain name, and the user inputs field values in the input boxes of the respective fields using the input unit.
S203, determining a corresponding data source set according to the domain name.
The computer equipment is pre-stored or pre-configured with a mapping relation between the domain names and the data source identifiers, wherein one domain name corresponds to a plurality of data sources in the mapping relation, and the data sources can be in the form of data such as databases, arrays or queues. The plurality of data sources constitute a data source set, and the computer device determines a corresponding data source set based on the mapping relationship according to the domain name configured in S202.
S204, selecting one data source from the data source set to be allocated to the component.
Wherein one of the data sources is selected as the data source for the component in the set of data sources, the component subsequently performing data operations in the data source, such as: read data or write data, etc.
In some embodiments, the data source is a database;
wherein said selecting a data source from said set of data sources for allocation to a component comprises:
selecting a database from the set of data sources;
binding the database name, the database type, the database connection address and the database account number of the selected data source with the component identifier.
For example, referring to the data source configuration page shown in fig. 4, the computer device displays the data source configuration page shown in fig. 4 through the display unit, the data source configuration page is provided with a database list, the database list includes two databases, and attribute fields of the databases include: the method comprises the steps of selecting one row of a database in a database list through an input unit by a user, binding field values of attribute fields of the selected database with component identifiers, and realizing the distribution of independent databases of all components.
S205, generating a component data source configuration file in a configuration center according to the domain name and the data source identification of each component.
After the configuration of the domain names and the data sources of the components is completed, generating component data source configuration files according to the domain names and the data source identifiers of the components, wherein each component independently generates one component data source configuration file, namely, the component data source configuration files are isolated according to the components, and the configuration center can be a Nacos-based center.
Further, the number of component occurrences referenced by the application (deleted components or added components) or component code (e.g., component version changes) is updated, the domain name and data source are reconfigured for the updated component, and then the component data source configuration file for the updated component is regenerated. When the component code is updated, the regenerated component data source configuration file will overwrite the original component data source configuration file.
In the embodiment of the application, the sandbox configuration information can be automatically generated and managed through the configuration center, and the sandbox configuration information represents relevant attributes of the sandbox, for example: the data source and the data source configuration information of the related components are automatically generated through the configuration of the data source and the components in the field, so that the development efficiency is improved, and the configuration error probability caused by unfamiliar flow of a user is reduced.
S206, running the application program in the sandbox.
Each deployed application program is provided with a sandbox, and each application program operates in different sandboxes, so that data isolation among the application programs is realized, operation safety is enhanced, and data leakage is avoided. And the computer equipment starts the sandbox in the host computer and runs the application program in the sandbox according to the sandbox configuration information corresponding to the application program.
In some embodiments, the application program runs in the cloud server, and the computer device firstly configures deployment information of the application program, specifically including configuration of an application program database and configuration of host attribute configuration. The application reads data from and writes data to the database.
For example, referring to the application deployment configuration page shown in fig. 5, the user configures fields and field values through the application deployment configuration page, the fields including: database account numbers, database passwords, registry addresses, machine deployment IP, rediss server addresses, gateway addresses, deployment environments, memory sizes, etc.
In some embodiments, the sandbox provides a container isolation function, and performs multiple instance ranges such as data read operation or data write operation according to data sources associated with different domain names, that is, a host deploying an application program provides multiple access ports, each access port realizes different data source operations, and efficiency of the data source operations is improved.
S207, when the application program calls the component, determining a data source of the called component configuration according to the component data source configuration file.
S208, executing data operation in the configured data source through the called component.
Wherein, when the application program calls the component, an execution script of the component is initialized, for example: the execution script is a bean script, the execution script is loaded to a data source configured by the component, and data reading operation or intermittent operation is executed. For example: the data sources are processed using a code level domain closure, sandbox Util.
The computer equipment configures the domain name for each component and configures independent data sources for each component according to the domain name, then generates component data source configuration information according to the configuration, and executes data operation in the respective data sources of the components when the application program runs and invokes the components.
The embodiment of the application realizes the capabilities of multiple data sources of the components, access of the application according to the component sub-library and the like. The data sources of the components are flexibly configured through the component multi-data source configuration function provided by the intelligent integrated collaborative cloud platform application center, unified standard environment parameter access is provided based on the intelligent sandboxes, unified calling and data source management of the intelligent integrated collaborative cloud platform component library components are supported, and the capabilities of component multi-data sources, component-based access by applications and the like are realized. When an application calls multiple components, different databases can be corresponding to different components, and application data is isolated from component data. When a component is invoked by multiple applications, the supporting component accesses the quarantine data per application repository.
The embodiment of the application realizes a better support assembly research and development management mode. The method effectively solves the problem that the prior application deployment does not support multiple data sources of the components, flexibly configures the data sources of the application referencing components in an online configuration mode, automatically generates corresponding configuration files and scripts, does not need manual additional deployment processing under the online, supports component research and development better, and enables the intelligent integrated collaborative cloud platform component research and development capability to be more powerful and flexible.
The embodiment of the application perfects the full life cycle management of the component. Based on the intelligent integrated collaborative cloud platform component library component full life cycle management process, aiming at a component application part, the component multi-data source configuration capability of a reference component is increased, and the component full life cycle management is perfected.
The following are device embodiments of the present application, which may be used to perform method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.
Referring to fig. 6, a schematic structural diagram of a management apparatus for component data sources according to an exemplary embodiment of the present application is shown, which is hereinafter referred to as apparatus 6. The apparatus 6 may be implemented as all or part of a computer device by software, hardware or a combination of both. The device 6 comprises: a determination unit 601, a configuration unit 602, a selection unit 603, a generation unit 604, an operation unit 605, and an execution unit 606.
A determining unit 601, configured to determine a plurality of components referenced by an application program;
a configuration unit 602 configured to configure, for each component, a domain name of the component;
the determining unit 602 is further configured to determine a corresponding data source set according to the domain name;
a selection unit 603 for selecting one data source from the set of data sources to be assigned to a component;
a generating unit 604, configured to generate a component data source configuration file in a configuration center according to the domain name and the data source identifier of each component;
an operation unit 605 for operating the application program in a sandbox;
the determining unit 602 is further configured to determine, when the application invokes a component, a data source of the invoked component configuration according to the component data source configuration file;
and the execution unit 606 is used for executing data operation in the configured data source through the called component.
In one or more possible embodiments, the performing, by the invoked component, a data operation in a configured data source includes:
initializing an execution script of the component, and loading the execution script to a data source configured by the component to realize data operation on the data source.
In one or more possible embodiments, configuration unit 602 is further to:
configuring deployment information of an application program; wherein the deployment information includes: database information and host information.
In one or more possible embodiments, further comprising:
and the updating unit is used for regenerating the component data source configuration file of the component and the original data source configuration file covering the component when the component code of the component referenced by the application program is updated.
In one or more possible embodiments, the data source is a database;
wherein said selecting a data source from said set of data sources for allocation to a component comprises:
selecting a database from the set of data sources;
binding the database name, the database type, the database connection address and the database account number of the selected data source with the component identifier.
In one or more possible embodiments, the configuration center is a Nacos-based configuration center.
In one or more possible embodiments, the domain name includes: product domain identification, product line identification, and domain code.
It should be noted that, when the device 4 provided in the foregoing embodiment performs the management method of the component data source, only the division of the foregoing functional modules is used as an example, and in practical application, the foregoing functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules to complete all or part of the foregoing functions. In addition, the management device of the component data source provided in the above embodiment and the management method embodiment of the component data source belong to the same concept, which embody detailed implementation procedures and are not described herein.
The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.
The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are adapted to be loaded by a processor and execute the method steps of the embodiment shown in fig. 2, and the specific execution process may refer to the specific description of the embodiment shown in fig. 2, which is not repeated herein.
The present application also provides a computer program product storing at least one instruction that is loaded and executed by the processor to implement the method of managing component data sources as described in the various embodiments above.
Referring to fig. 7, a schematic structural diagram of a computer device is provided in an embodiment of the present application. As shown in fig. 7, the computer device 700 may include: at least one processor 701, at least one network interface 704, a user interface 703, a memory 705, at least one communication bus 702.
Wherein the communication bus 702 is used to enable connected communications between these components.
The user interface 703 may include a Display screen (Display), a Camera (Camera), and the optional user interface 703 may further include a standard wired interface, and a wireless interface.
The network interface 704 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
Wherein the processor 701 may include one or more processing cores. The processor 701 utilizes various interfaces and lines to connect various portions of the overall computer device 700, perform various functions of the computer device 700, and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 705, and invoking data stored in the memory 705. Alternatively, the processor 701 may be implemented in hardware in at least one of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 701 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 701 and may be implemented by a single chip.
The Memory 705 may include a random access Memory (Random Access Memory, RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 705 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). Memory 705 may be used to store instructions, programs, code, sets of codes, or instruction sets. The memory 705 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, etc.; the storage data area may store data or the like referred to in the above respective method embodiments. The memory 705 may also optionally be at least one storage device located remotely from the processor 701. As shown in fig. 7, an operating system, a network communication module, a user interface module, and application programs may be included in the memory 705, which is one type of computer storage medium.
In the computer device 700 shown in fig. 7, the user interface 703 is mainly used as an interface for providing input for a user, and obtains data input by the user; the processor 701 may be configured to invoke an application program stored in the memory 705 and specifically execute the method shown in fig. 2, and the specific process may be shown in fig. 2, which is not repeated herein.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory, a random access memory, or the like.
The foregoing disclosure is only illustrative of the preferred embodiments of the present application and is not intended to limit the scope of the claims herein, as the equivalent of the claims herein shall be construed to fall within the scope of the claims herein.

Claims (10)

1. A method for managing component data sources, comprising:
determining a plurality of components referenced by the application;
for each component, configuring a domain name of the component;
determining a corresponding data source set according to the domain name;
selecting one data source from the set of data sources to be allocated to a component;
generating a component data source configuration file in a configuration center according to the field name and the data source identifier of each component;
running the application in a sandbox;
when the application program calls a component, determining a data source of the called component configuration according to the component data source configuration file;
and executing data operation in the configured data source through the called component.
2. The method of claim 1, wherein the performing data operations in the configured data source by the invoked component comprises:
initializing an execution script of the component, and loading the execution script to a data source configured by the component to realize data operation on the data source.
3. The method of claim 1 or 2, wherein prior to determining the plurality of components referenced by the application, further comprising:
configuring deployment information of an application program; wherein the deployment information includes: database information and host information.
4. A method according to claim 3, further comprising:
when the component code of the component referenced by the application program is updated, the component data source configuration file of the component and the original data source configuration file covering the component are regenerated.
5. The method of claim 1 or 2 or 4, wherein the data source is a database;
wherein said selecting a data source from said set of data sources for allocation to a component comprises:
selecting a database from the set of data sources;
binding the database name, the database type, the database connection address and the database account number of the selected data source with the component identifier.
6. The method of claim 5, wherein the configuration center is a Nacos-based configuration center.
7. The method of claim 1 or 2 or 4 or 6, wherein the domain name comprises: product domain identification, product line identification, and domain code.
8. A management apparatus for a component data source, comprising:
a determining unit configured to determine a plurality of components referenced by the application program;
a configuration unit configured to configure, for each component, a domain name of the component;
the determining unit is further used for determining a corresponding data source set according to the domain name;
a selection unit for selecting one data source from the set of data sources to be allocated to a component;
the generating unit is used for generating a component data source configuration file in the configuration center according to the domain name and the data source identifier of each component;
the operation unit is used for operating the application program in the sandbox;
the determining unit is further used for determining a data source of the called component configuration according to the component data source configuration file when the application program calls the component;
and the execution unit is used for executing data operation in the configured data source through the called component.
9. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the method steps of any one of claims 1 to 7.
10. A computer device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1-7.
CN202211341068.7A 2022-10-30 2022-10-30 Method and device for managing component data sources, storage medium and computer equipment Pending CN116049166A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211341068.7A CN116049166A (en) 2022-10-30 2022-10-30 Method and device for managing component data sources, storage medium and computer equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211341068.7A CN116049166A (en) 2022-10-30 2022-10-30 Method and device for managing component data sources, storage medium and computer equipment

Publications (1)

Publication Number Publication Date
CN116049166A true CN116049166A (en) 2023-05-02

Family

ID=86112178

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211341068.7A Pending CN116049166A (en) 2022-10-30 2022-10-30 Method and device for managing component data sources, storage medium and computer equipment

Country Status (1)

Country Link
CN (1) CN116049166A (en)

Similar Documents

Publication Publication Date Title
CN111078315B (en) Microservice arranging and executing method and system, architecture, equipment and storage medium
US20210117210A1 (en) Methods and Systems for Integrated Development Environment Editor Support with a Single Code Base
US7174361B1 (en) Scripting task-level user-interfaces
WO2016155388A1 (en) Method and device for installing and running application
US8332431B2 (en) Configuration information management apparatus, configuration information management program, and configuration information management method
US11797273B2 (en) System and method for enhancing component based development models with auto-wiring
CN111309216B (en) List page display method and device, computer equipment and storage medium
US11741002B2 (en) Test automation systems and methods using logical identifiers
US8176097B2 (en) Maintaining data coherency within related multi-perspective user interfaces via session-less queries
CN108804100B (en) Method and device for creating interface element, storage medium and mobile terminal
CN113971037A (en) Application processing method and device, electronic equipment and storage medium
JP7174107B2 (en) Scheduling method, device, facility, storage facility, and program
CN110096543B (en) Data operation method, device, server and medium of application program
CN113296758A (en) Front-end component library construction method and device and storage medium
CN110221910B (en) Method and apparatus for performing MPI jobs
US20220311662A1 (en) Network configuring method for cloud mobile phone, device and storage medium
CN116049166A (en) Method and device for managing component data sources, storage medium and computer equipment
CN115359145A (en) Method and device for drawing process graphics primitives, storage medium and computer equipment
US11640281B2 (en) Tool for introspection in object-oriented source code
CN114679491A (en) Micro front-end service application method and device, storage medium and electronic equipment
CN111124386A (en) Unity-based animation event processing method, device, equipment and storage medium
CN116775030B (en) Method and device for creating security baseline
CN115730096A (en) Primitive customization method and device, storage medium and computer equipment
CN108804101B (en) Method and device for creating interface element, storage medium and mobile terminal
CN115048180A (en) Operation method and device of virtual machine check point, storage medium and computer equipment

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