CN111399812B

CN111399812B - Component construction method and device, development framework and equipment

Info

Publication number: CN111399812B
Application number: CN202010266791.8A
Authority: CN
Inventors: 李宁; 宋杨
Original assignee: Chongqing Cloud Core Intelligent Technology Co ltd; Hangzhou Diji Intelligent Technology Co ltd
Current assignee: Chongqing Cloud Core Intelligent Technology Co ltd; Hangzhou Diji Intelligent Technology Co ltd
Priority date: 2020-04-07
Filing date: 2020-04-07
Publication date: 2022-04-19
Anticipated expiration: 2040-04-07
Also published as: CN111399812A

Abstract

The embodiment of the specification provides a component construction method, a device, a development framework and equipment, wherein the method comprises the following steps: selecting a member for constructing a target component from members registered in a development framework; according to the service logic of the target assembly, appointing the jump logic between the selected components, wherein the jump logic comprises the jump sequence and the transmission parameters between the components; and triggering the development framework to execute corresponding components according to the jump logic by the constructed target component so as to realize the business logic. The technical scheme of the embodiment of the specification is used for solving the problem that the existing development framework still needs to carry out code programming on the components when a system is built and updated, so that the labor cost and the time cost are high.

Description

Component construction method and device, development framework and equipment

Technical Field

The present disclosure relates to the field of computers, and in particular, to a method and an apparatus for constructing a component, a development framework, and a device.

Background

With the explosive growth of intelligent hardware and intelligent networks, various industries and various scenes such as manufacturing workshops, gardens, streets, intelligent buildings, intelligent parks and even testing are intelligentized, and the intelligentized scenes urgently need a system capable of fast iterating to digitize equipment and carry out unified and coordinated comprehensive management on the equipment.

At present, intelligent equipment and a network can well support pluggable in physics and are in rapid updating iteration and upgrading, and a good development framework is needed for the intelligent equipment and the network, so that zero-code programming can be realized when components and applications are updated by the intelligent equipment and the network, and updating iteration matched with a system can be realized only by hot plugging and arranging the components and the components.

Disclosure of Invention

The specification provides a component construction method, a component construction device, a development framework and equipment, which are used for solving the problem that the existing development framework still needs to carry out code programming on components when a system is built and updated, so that the labor cost and the time cost are high.

In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:

in a first aspect, an embodiment of the present specification provides an assembly building method, including:

selecting a member for constructing a target component from members registered in a development framework;

according to the service logic of the target assembly, appointing the jump logic between the selected components, wherein the jump logic comprises the jump sequence and the transmission parameters between the components;

and triggering the development framework to execute corresponding components according to the jump logic by the constructed target component so as to realize the business logic.

In a second aspect, embodiments of the present specification provide an assembly construction apparatus, comprising:

a component selection module that selects a component for constructing a target component from components that have been registered in the development framework;

the logic agreement module is used for agreeing the jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises the jump sequence and the transmission parameters between the components;

In a third aspect, embodiments of the present specification provide a development framework, including:

the registration issuing module is used for receiving registration information of the component to be registered and issuing the registration information in the development framework so as to complete registration of the corresponding component;

the routing module is used for receiving a uniform resource identifier issued by a target component, wherein the uniform resource identifier carries the position of a resource of a component and an input parameter; constructing a route from the position of the resource in the uniform resource identifier to the position of the resource, and acquiring a corresponding component from the position of the resource based on the constructed route;

the engine module is used for creating an engine instance corresponding to the component type based on the acquired component type corresponding to the component; and loading the engine instance and the input parameters in the uniform resource identifier into a specified engine for execution, and returning the obtained output parameters to the target component.

In a fourth aspect, embodiments of the present specification provide an assembly building apparatus, including:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

In a fifth aspect, embodiments of the present specification provide a storage medium. The storage medium is used to store computer-executable instructions. The computer executable instructions, when executed, implement the following process:

According to the component construction method, the component construction device, the development framework and the equipment, components for constructing target components are selected from components registered in the development framework; appointing a jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises a jump sequence and a transmission parameter between the components; and triggering the development framework to execute corresponding components according to the jump logic so as to realize the business logic. In the embodiment of the specification, because the components are registered to perform resource management in the development framework and are not solidified in the preset component in a hard code manner, the components contained in the component and the jump logic between the components can be flexibly appointed and changed when the target component is built. When the system is actually updated, as long as the component granularity is sufficiently refined, the target component can be quickly constructed by changing the components contained in the component and the jump logic among the components, and the component does not need to be additionally programmed by codes, so that the labor and time costs are reduced.

Drawings

In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and that other drawings can be obtained by those skilled in the art without inventive exercise.

FIG. 1 is a schematic diagram of a logical architecture of a component construction method provided in an embodiment of the present disclosure;

FIG. 2 is a first flowchart of a component construction method provided in an embodiment of the present disclosure;

fig. 3 is a second flowchart of a component construction method provided in an embodiment of the present specification;

FIG. 4 is a third schematic flowchart of a component construction method provided in an embodiment of the present disclosure;

FIG. 5 is a block diagram of an assembly building apparatus provided in an embodiment of the present disclosure;

fig. 6 is a schematic diagram of module composition of a development framework provided in an embodiment of the present specification;

fig. 7 is a schematic structural diagram of an assembly building apparatus provided in an embodiment of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the embodiments of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

Fig. 1 is a schematic diagram of a logic architecture of an element construction method provided in an embodiment of the present specification, and as shown in fig. 1, the logic architecture is hierarchically divided from top to bottom, including: applications, components, members, and development frameworks for executing members; wherein, an application can comprise a plurality of assemblies, each assembly can be composed of a plurality of components (such as a component A, a component B and a component C); all the components contained in one component are loaded and executed by the development framework according to the appointed jump logic, and the business logic defined by the component can be realized. The development framework in the specification comprises a registration and release module (Register), a routing module (route) and an engine module (engine); wherein:

the registration issuing module is used for receiving the registration information of the component to be registered and issuing the registration information in the development framework so as to complete the registration of the corresponding component, and the registered component can be searched and executed in the development framework; each component can adopt a unique uniform resource identifier for component resource management, and the uniform resource identifier comprises the position of the resource of the component and input parameters required when the component is executed.

the engine module is used for creating an engine instance corresponding to the component type based on the component type corresponding to the component acquired by the routing module; and loading the input parameters in the engine instance and the uniform resource identifier into a specified engine for execution, and returning the obtained output parameters to the target component.

In the process of constructing the target component, a technical developer needs to select a component for constructing the target component from components registered in a development framework; in order to realize zero-code building components as much as possible, the granularity of components registered in the development framework is sufficiently fine, and the number of components is also large. After the components are selected, according to the service logic of the target component, the jump logic between the selected components is appointed, wherein the jump logic comprises the jump sequence and the transmission parameters between the components; after the jump logic is agreed and completed, the component construction is considered to be completed. And triggering the development framework to execute the corresponding component according to the jump logic by the constructed target component so as to realize the business logic.

Further, the component resources are managed based on the uniform resource identifiers, namely each component corresponds to one uniform resource identifier, and the uniform resource identifiers carry the positions of the components and input parameters;

correspondingly, when the jump logic between the selected components is agreed according to the service logic of the target component, the calling sequence between the uniform resource identifiers corresponding to the selected components and the parameter values of the input parameters in the uniform resource identifiers can be agreed according to the service logic of the target component. It can be seen that the finally formed target component is exposed to the outside by an ordered string of uniform resource identifiers, and may also be a call interface (e.g., RESTful API interface) formed after the ordered string of uniform resource identifiers is encapsulated.

Further, the process of triggering the development framework to execute the corresponding component to realize the business logic according to the jump logic by the target component may specifically be:

the target component firstly sends a first uniform resource identifier to be called to a development framework; after receiving the first uniform resource identifier to be called, the development framework searches for a corresponding component according to the position of the resource in the first uniform resource identifier to be called; the development framework loads and executes the searched component and the input parameter in the first uniform resource identifier to be called, and returns the obtained output parameter to the target component; after receiving the output parameter, the target component generates an input parameter in a second uniform resource identifier to be called according to the output parameter, and sends the formed second uniform resource identifier to be called to the development framework; after receiving the second uniform resource identifier to be called, the development framework performs the same operation by analogy with the operation flow aiming at the first uniform resource identifier to be called; and repeating the steps until the target component sends the formed last uniform resource identifier to be called to the development framework, and acquiring the output parameters returned by the development framework based on the last uniform resource identifier to be called. The output parameter is the final parameter output by the target component after the target component executes the business logic once.

Further, when the development framework searches for the corresponding component according to the location of the resource in the first uniform resource identifier to be called, the routing module in the development framework may construct a route to the location of the resource according to the location of the resource in the first uniform resource identifier to be called, and search for the corresponding component from the location of the resource based on the constructed route.

Further, when the searched component and the input parameter in the first uniform resource identifier to be called are loaded and executed, and the obtained output parameter is returned to the target component, an engine instance corresponding to the component type can be created by an engine module in the development framework based on the component type corresponding to the searched component; and loading the engine instance and the input parameters in the first uniform resource identifier to be called into a specified engine for execution, and returning the obtained output parameters to the target component.

Further, while the component construction process is executed, a new component can be created based on the updating requirement of the business logic, and the new component is registered in the development framework; and/or modifying and/or deleting the registered components based on the updating requirement of the business logic so as to be called and executed by the target component or other components to be constructed.

The technical solution of the present specification is further illustrated by the following examples.

Example one

Based on the application scenario architecture, fig. 2 is a first flowchart of a component building method provided in an embodiment of the present specification, where the method in fig. 2 can be executed by the development framework in fig. 1, as shown in fig. 2, the method includes the following steps:

in step S102, a component for constructing a target component is selected from components that have been registered in the development framework.

The components in the embodiment of the present specification are not solidified (programmed by codes) in preset components of the development framework, but are stored in the development framework by means of registration, and there is no solidified correspondence between each component and each component. The components can be developed in a fine-grained manner and then registered in a development framework, and the development framework can operate the component resources registered in the framework, including searching and loading execution of the components. Registration information corresponding to registered components may include, but is not limited to: the resource location of the component, input parameters, component type, component function and the like.

Specifically, the technical developer may select a member for constructing the target component according to a function to be realized by the target component to be constructed, and with reference to registration information of members registered in the development framework.

Step S104, according to the service logic of the target assembly, appointing the jump logic between the selected components, wherein the jump logic comprises the jump sequence and the transmission parameters between the components;

and triggering the development framework to execute the corresponding component according to the jump logic by the constructed target component so as to realize the business logic.

Specifically, after selecting the components for constructing the target component, the jump sequence between the components and the parameter transfer in the jump process can be reasonably arranged according to the service logic to be realized by the target component, that is, the jump logic between the selected components is agreed, and the jump logic includes the jump sequence between the components and the transfer parameter.

After the engagement completes the jump logic between the selected components, the target component is constructed. And triggering the development framework to execute the corresponding component according to the appointed jump logic of the constructed target component so as to realize the business logic of the target component.

In the embodiment of the specification, the target component is based on the jump logic between the appointed components and the corresponding components which are registered in the development framework to drive the development framework to load and execute the corresponding components so as to realize the business logic of the target component. The method reduces the strong coupling between the components and flexibly realizes the construction process from component to component; meanwhile, the components are stored in the development framework in a registration mode, so that the management of the components can be independently and flexibly realized under the condition of not considering the service logic of the components, the research and the development of the components are conveniently realized, and zero codes of the components are updated.

The component construction method provided by the embodiment of the specification selects a component for constructing a target component from components registered in a development framework; appointing a jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises a jump sequence and a transmission parameter between the components; and triggering the development framework to execute corresponding components according to the jump logic so as to realize the business logic. In the embodiment of the specification, because the components are registered to perform resource management in the development framework and are not solidified in the preset component in a hard code manner, the components contained in the component and the jump logic between the components can be flexibly appointed and changed when the target component is built. When the system is actually updated, as long as the component granularity is sufficiently refined, the target component can be quickly constructed by changing the components contained in the component and the jump logic among the components, and the component does not need to be additionally programmed by codes, so that the labor and time costs are reduced.

Example two

The embodiment expands and supplements the component construction method shown in fig. 2 on the basis of the first embodiment.

Further, in this specification, each component corresponds to a uniform resource identifier, and the uniform resource identifier carries a location of a resource of the component and an input parameter. Accordingly, as shown in fig. 3, the step S104 may include:

s104-2, according to the service logic of the target assembly, appointing the calling sequence between the uniform resource identifiers corresponding to the selected components and the parameter values of the input parameters in the uniform resource identifiers.

Specifically, when the jump logic between the selected components is agreed, the call sequence between the uniform resource identifiers corresponding to the selected components and the parameter values of the input parameters in the uniform resource identifiers may be specifically agreed. It can be seen that the finally formed target component is exposed to the outside by an ordered string of uniform resource identifiers, and may also be a call interface (e.g., RESTful API interface) formed after the ordered string of uniform resource identifiers is encapsulated.

On this basis, as described in fig. 4, the step of triggering the development framework to execute the corresponding component to implement the business logic according to the jump logic by the target component may include:

s112, the target component sends the first uniform resource identifier to be called to the development framework.

After the target component is formed, the uniform resource identifiers of the components to be executed are sequentially sent to the development framework according to the jump logic. The sent first uniform resource identifier to be called comprises the resource position and the input parameter of the first component to be executed, wherein the input parameter is provided when the external service program calls the target component.

S114, the development framework searches a corresponding component according to the position of the resource in the first uniform resource identifier to be called; and loading and executing the searched component and the input parameter in the first uniform resource identifier to be called, and returning the obtained output parameter to the target component.

Firstly, after receiving a first uniform resource identifier to be called, a development framework searches a corresponding component according to the position of a resource in the first uniform resource identifier to be called. For example, a routing module in the development framework constructs a route to the location of the resource according to the location of the resource in the first uniform resource identifier to be called, and searches the corresponding component from the location of the resource based on the constructed route. Specifically, after receiving the first uniform resource identifier to be called, the routing module analyzes the uniform resource identifier, extracts the position of the resource from the uniform resource identifier, constructs a route to the position of the resource, and acquires a corresponding component from the position of the resource based on the constructed route.

And then, the development framework loads and executes the searched component and the input parameter in the first uniform resource identifier to be called, and returns the obtained output parameter to the target component. For example, an engine module in the development framework creates an engine instance corresponding to the component type based on the component type corresponding to the found component; and then loading the engine instance and the input parameters in the first uniform resource identifier to be called into a specified engine for execution, and returning the obtained output parameters to the target component. Specifically, after the engine module acquires the component, the type of the component is identified firstly, then an engine instance corresponding to the component type is created, after the creation is completed, the engine instance is loaded into a specified engine to be executed, meanwhile, an input parameter in a first uniform resource identifier to be called is also loaded in the engine, and the input parameter is used as an input parameter when the component is executed; and finally, the engine module returns the output parameters obtained by the execution component to the target component.

S116, the target component generates an input parameter in a second uniform resource identifier to be called according to the output parameter, and sends the formed second uniform resource identifier to be called to the development framework; and repeating the steps until the target component sends the formed last uniform resource identifier to be called to the development frame, and acquiring the output parameters returned by the development frame based on the last uniform resource identifier to be called.

Specifically, after receiving an output parameter returned by the development frame based on the first uniform resource identifier to be called, the target component generates an input parameter in a second uniform resource identifier to be called according to the output parameter, and recombines the input parameter with the position information of the resource in the second uniform resource identifier to be called to form the uniform resource identifier which can be called. The target component sends the formed second uniform resource identifier to be called to the development framework; and after receiving the second uniform resource identifier to be called, the development framework can refer to the execution process of the previous step, perform equal processing on the second uniform resource identifier to be called, and return output parameters after the processing is performed on the second uniform resource identifier to be called to the target component. And repeating the steps until the target component forms the last uniform resource identifier to be called based on the output parameter generated by executing the processing aiming at the last uniform resource identifier to be called, sends the last uniform resource identifier to be called to the development frame, and acquires the output parameter returned by the development frame based on the last uniform resource identifier to be called. The output parameter is the final parameter output by the target component after the target component executes the business logic once.

Further, the component construction method further comprises the following steps:

creating a new component based on the updating requirement of the business logic, and registering the new component into a development framework; and/or modifying and/or deleting registered components based on the need for updates to the business logic.

Specifically, when the business logic of the completed target component needs to be updated or the business logic needs to be expanded, a new component can be created separately and registered in the development framework, or the registered component can be modified and/or deleted based on the updating requirement of the business logic, so that the component construction requirement suitable for different business logics can be continuously met by continuously updating the registered component in the development framework.

EXAMPLE III

On the basis of the same technical concept, the embodiment of the present specification further provides an assembly construction apparatus corresponding to the assembly construction method described in fig. 2 to 4. Fig. 5 is a schematic diagram of a module composition of an assembly building apparatus provided in an embodiment of the present specification, the apparatus being configured to perform the assembly building method described in fig. 2 to 4, and as shown in fig. 5, the apparatus includes:

a component selection module 201 that selects a component for constructing a target component from among components that have been registered in the development framework;

a logic agreement module 202, which agrees the jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises the jump sequence and the transmission parameters between the components;

The component construction apparatus provided in the embodiments of the present specification selects a component for constructing a target component from components that have been registered in a development framework; appointing a jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises a jump sequence and a transmission parameter between the components; and triggering the development framework to execute corresponding components according to the jump logic so as to realize the business logic. In the embodiment of the specification, because the components are registered to perform resource management in the development framework and are not solidified in the preset component in a hard code manner, the components contained in the component and the jump logic between the components can be flexibly appointed and changed when the target component is built. When the system is actually updated, as long as the component granularity is sufficiently refined, the target component can be quickly constructed by changing the components contained in the component and the jump logic among the components, and the component does not need to be additionally programmed by codes, so that the labor and time costs are reduced.

Optionally, each component corresponds to a uniform resource identifier, and the uniform resource identifier carries the position of the resource of the component and the input parameter;

correspondingly, the logic agreement module 202 agrees the calling sequence between the uniform resource identifiers corresponding to the selected component and the parameter values of the input parameters in the uniform resource identifiers according to the service logic of the target component.

Optionally, the triggering, by the target component, the development framework to execute the corresponding component to implement the service according to the jump logic includes:

the target component sends a first uniform resource identifier to be called to the development framework;

the development framework searches a corresponding component according to the position of the resource in the first uniform resource identifier to be called; loading and executing the searched component and the input parameter in the first uniform resource identifier to be called, and returning the obtained output parameter to the target component;

and the target component generates an input parameter in the second uniform resource identifier to be called according to the output parameter, sends the formed second uniform resource identifier to be called to the development frame, and so on until the target component sends the formed last uniform resource identifier to be called to the development frame and obtains the output parameter returned by the development frame based on the last uniform resource identifier to be called.

Optionally, the step of the development framework searching for the corresponding component according to the location of the resource in the first uniform resource identifier to be called includes:

and a routing module in the development framework constructs a route from the position of the resource in the first uniform resource identifier to be called to the position of the resource, and acquires a corresponding component from the position of the resource based on the constructed route.

Optionally, loading and executing the searched component and the input parameter in the first uniform resource identifier to be called, and returning the obtained output parameter to the target component includes:

an engine module in the development framework is used for creating an engine instance corresponding to the component type based on the component type corresponding to the searched component; and loading the engine instance and the input parameters in the first uniform resource identifier to be called into a specified engine for execution, and returning the obtained output parameters to the target component.

Optionally, the component construction apparatus further comprises:

the component management module is used for creating a new component based on the updating requirement of the business logic and registering the new component into the development framework; and/or the presence of a gas in the gas,

registered components are modified and/or deleted based on the need for updates to the business logic.

Example four

Based on the same technical concept, the embodiment of the present specification further provides a development framework corresponding to the component construction method described in fig. 2 to 4, as shown in fig. 6, the development framework includes:

the registration issuing module 210 receives registration information of a component to be registered, and issues the registration information in the development framework to complete registration of the corresponding component;

the routing module 220 receives a uniform resource identifier issued by the target component, wherein the uniform resource identifier carries the position of the resource of the component and the input parameter; constructing a route from the position of the resource in the uniform resource identifier to the position of the resource, and acquiring a corresponding component from the position of the resource based on the constructed route;

the engine module 230, which creates an engine instance corresponding to the component type based on the component type corresponding to the acquired component; and loading the input parameters in the engine instance and the uniform resource identifier into a specified engine for execution, and returning the obtained output parameters to the target component.

The development framework provided by the embodiment of the present specification can participate in executing the component construction method shown in the above embodiment, and selects a component for constructing a target component from components registered in the development framework; appointing a jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises a jump sequence and a transmission parameter between the components; and triggering the development framework to execute corresponding components according to the jump logic so as to realize the business logic. In the embodiment of the specification, because the components are registered to perform resource management in the development framework and are not solidified in the preset component in a hard code manner, the components contained in the component and the jump logic between the components can be flexibly appointed and changed when the target component is built. When the system is actually updated, as long as the component granularity is sufficiently refined, the target component can be quickly constructed by changing the components contained in the component and the jump logic among the components, and the component does not need to be additionally programmed by codes, so that the labor and time costs are reduced.

EXAMPLE five

On the basis of the same technical concept, the embodiment of the present specification further provides a component construction apparatus for performing the component construction method described above, corresponding to the component construction method described above with reference to fig. 2 to 4, and fig. 7 is a schematic structural diagram of the component construction apparatus provided in the embodiment of the present specification.

As shown in fig. 7, the component building apparatus may have a relatively large difference due to different configurations or performances, and may include one or more processors 301 and a memory 302, where the memory 302 may store one or more stored applications or data. Memory 302 may be, among other things, transient storage or persistent storage. The application program stored in memory 302 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a component construction device. Still further, the processor 301 may be arranged in communication with the memory 302 to execute a series of computer executable instructions in the memory 302 on the component construction device. The component building apparatus may also include one or more power supplies 303, one or more wired or wireless network interfaces 304, one or more input-output interfaces 305, one or more keyboards 306, and the like.

In a particular embodiment, the component construction apparatus comprises a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may comprise one or more modules, and each module may comprise a series of computer-executable instructions for the component construction apparatus, and the one or more programs configured to be executed by the one or more processors comprise computer-executable instructions for:

Optionally, when the computer-executable instruction is executed, each component corresponds to one uniform resource identifier, and the uniform resource identifier carries a position of a resource of the component and an input parameter;

the appointing the jump logic between the selected components according to the service logic of the target component comprises:

and appointing a calling sequence between uniform resource identifiers corresponding to the selected components and parameter values of the input parameters in the uniform resource identifiers according to the service logic of the target component.

Optionally, when executed, the target component triggering the development framework to execute the corresponding component to implement the business logic according to the jump logic includes:

the development framework searches a corresponding component according to the position of the resource in the first uniform resource identifier to be called;

loading and executing the searched component and the input parameter in the first uniform resource identifier to be called, and returning the obtained output parameter to the target component;

and the target component generates an input parameter in a second uniform resource identifier to be called according to the output parameter, sends the formed second uniform resource identifier to be called to the development frame, and so on until the target component sends the formed last uniform resource identifier to be called to the development frame and obtains the output parameter returned by the development frame based on the last uniform resource identifier to be called.

Optionally, when the computer executable instructions are executed, the finding, by the development framework, the corresponding component according to the location of the resource in the first uniform resource identifier to be called includes:

and the routing module in the development framework constructs a route from the position of the resource in the first uniform resource identifier to be called to the position of the resource, and searches a corresponding component from the position of the resource based on the constructed route.

Optionally, when executed, the loading and executing the searched component and the input parameter in the first uniform resource identifier to be called, and returning the obtained output parameter to the target component includes:

the engine module in the development framework establishes an engine instance corresponding to the component type based on the component type corresponding to the searched component; and loading the engine instance and the input parameters in the first uniform resource identifier to be called into a specified engine for execution, and returning the obtained output parameters to the target component.

Optionally, the computer executable instructions, when executed, further comprise:

creating a new component based on the updating requirement of the business logic, and registering the new component into the development framework; and/or the presence of a gas in the gas,

The component construction device provided by the embodiment of the specification selects a component for constructing a target component from components registered in a development framework; appointing a jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises a jump sequence and a transmission parameter between the components; and triggering the development framework to execute corresponding components according to the jump logic so as to realize the business logic. In the embodiment of the specification, because the components are registered to perform resource management in the development framework and are not solidified in the preset component in a hard code manner, the components contained in the component and the jump logic between the components can be flexibly appointed and changed when the target component is built. When the system is actually updated, as long as the component granularity is sufficiently refined, the target component can be quickly constructed by changing the components contained in the component and the jump logic among the components, and the component does not need to be additionally programmed by codes, so that the labor and time costs are reduced.

It should be noted that the embodiment of the component constructing apparatus in this specification and the embodiment of the component constructing method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the component constructing method described above, and repeated details are not described again.

EXAMPLE six

Based on the same technical concept, the embodiment of the present disclosure further provides a storage medium for storing computer-executable instructions, where in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, and the like, and when being executed by a processor, the storage medium stores the computer-executable instructions, which can implement the following processes:

The computer-executable instructions stored in the storage medium provided in the embodiments of the present specification, when executed by the processor, select a component for constructing a target component from among components already registered in the development framework; appointing a jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises a jump sequence and a transmission parameter between the components; and triggering the development framework to execute corresponding components according to the jump logic so as to realize the business logic. In the embodiment of the specification, because the components are registered to perform resource management in the development framework and are not solidified in the preset component in a hard code manner, the components contained in the component and the jump logic between the components can be flexibly appointed and changed when the target component is built. When the system is actually updated, as long as the component granularity is sufficiently refined, the target component can be quickly constructed by changing the components contained in the component and the jump logic among the components, and the component does not need to be additionally programmed by codes, so that the labor and time costs are reduced.

Optionally, when the computer-executable instructions stored in the storage medium are executed by the processor, each component corresponds to one uniform resource identifier, and the uniform resource identifier carries a position of a resource of the component and an input parameter;

Optionally, when executed by a processor, the target component triggers the development framework to execute the corresponding components according to the jump logic to implement the business logic, including:

Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the finding, by the development framework, the corresponding component according to the location of the resource in the first uniform resource identifier to be called includes:

Optionally, when executed by a processor, the loading and executing the searched component and the input parameter in the first uniform resource identifier to be called, and returning the obtained output parameter to the target component includes:

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, further comprise:

The computer-executable instructions stored in the storage medium provided by the embodiment of the specification are executed by the processor, and the components used for constructing the target component are selected from the components registered in the development framework; appointing a jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises a jump sequence and a transmission parameter between the components; and triggering the development framework to execute corresponding components according to the jump logic so as to realize the business logic. In the embodiment of the specification, because the components are registered to perform resource management in the development framework and are not solidified in the preset component in a hard code manner, the components contained in the component and the jump logic between the components can be flexibly appointed and changed when the target component is built. When the system is actually updated, as long as the component granularity is sufficiently refined, the target component can be quickly constructed by changing the components contained in the component and the jump logic among the components, and the component does not need to be additionally programmed by codes, so that the labor and time costs are reduced.

It should be noted that the embodiment of the storage medium in this specification and the embodiment of the component construction method in this specification are based on the same inventive concept, and therefore specific implementation of this embodiment may refer to implementation of the component construction method described above, and repeated details are not described again.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain a corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that 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 like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. A component construction method, comprising:

selecting a member for constructing a target component from members registered in a development framework; each component corresponds to a uniform resource identifier, and the uniform resource identifier carries the position of the resource of the component and an input parameter;

according to the service logic of the target assembly, appointing the jump logic between the selected components, wherein the jump logic comprises the jump sequence and the transmission parameters between the components; the appointing the jump logic between the selected components according to the service logic of the target component comprises:

appointing a calling sequence between uniform resource identifiers corresponding to the selected components and parameter values of the input parameters in the uniform resource identifiers according to the service logic of the target component;

the constructed target assembly triggers the development framework to execute a corresponding component according to the jump logic so as to realize the business logic; the target component triggering the development framework to execute corresponding components according to the jump logic to realize the business logic comprises the following steps:

2. The method of claim 1, wherein the step of the development framework searching for the corresponding component according to the location of the resource in the first uniform resource identifier to be called comprises:

3. The method of claim 1, wherein the loading and executing the searched component and the input parameter in the first uniform resource identifier to be called, and returning the obtained output parameter to the target component comprises:

4. The method of claim 1, further comprising:

5. An assembly building apparatus comprising:

a component selection module that selects a component for constructing a target component from components that have been registered in the development framework; each component corresponds to a uniform resource identifier, and the uniform resource identifier carries the position of the resource of the component and an input parameter;

the logic agreement module is used for agreeing the jump logic between the selected components according to the service logic of the target component, wherein the jump logic comprises the jump sequence and the transmission parameters between the components; the appointing the jump logic between the selected components according to the service logic of the target component comprises:

6. An assembly building apparatus comprising:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions which, when executed by the processor, implement the steps of the component construction method of any one of claims 1 to 4.

7. A storage medium storing computer-executable instructions which, when executed by a processor, implement the steps of the component construction method according to any one of claims 1-4.