WO2020199594A1 - 业务组件加载方法、装置、计算机设备和存储介质 - Google Patents
业务组件加载方法、装置、计算机设备和存储介质 Download PDFInfo
- Publication number
- WO2020199594A1 WO2020199594A1 PCT/CN2019/117330 CN2019117330W WO2020199594A1 WO 2020199594 A1 WO2020199594 A1 WO 2020199594A1 CN 2019117330 W CN2019117330 W CN 2019117330W WO 2020199594 A1 WO2020199594 A1 WO 2020199594A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- component
- business
- identifier
- resource pool
- preset
- 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.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Definitions
- This application relates to a service component loading method, device, computer equipment and storage medium.
- a service component loading method, device, computer equipment, and storage medium are provided.
- a method for loading business components including:
- the call instruction carries the caller ID and the component ID, and look up the caller ID in the preset permission table according to the load instruction;
- the callable component ID corresponding to the caller ID is obtained;
- the business component corresponding to the component identifier is copied from the preset resource pool, and the business component is returned to the terminal, so that the terminal loads the business component.
- a service component loading device including:
- the identification lookup module is used to receive the service component loading instruction, the calling instruction carries the caller identification and the component identification, and the caller identification is searched in the preset permission table according to the loading instruction;
- the component identification obtaining module is used to obtain the callable component identification corresponding to the caller identification when the caller identification is found in the preset permission table;
- the component loading module is used to copy the business component corresponding to the component identification from the preset resource pool when the component identification exists in the callable component identification, and return the business component to the terminal so that the terminal loads the business component.
- a computer device including a memory and one or more processors, the memory stores computer readable instructions, when the computer readable instructions are executed by the processor, the one or more processors execute The following steps:
- the call instruction carries the caller ID and the component ID, and look up the caller ID in the preset permission table according to the load instruction;
- the business component corresponding to the component identifier is copied from the preset resource pool, and the business component is returned to the terminal, so that the terminal loads the business component.
- One or more non-volatile storage media storing computer-readable instructions.
- the computer-readable instructions When executed by one or more processors, the one or more processors perform the following steps:
- the call instruction carries the caller ID and the component ID, and look up the caller ID in the preset permission table according to the load instruction;
- the business component corresponding to the component identifier is copied from the preset resource pool, and the business component is returned to the terminal, so that the terminal loads the business component.
- Fig. 1 is an application scenario diagram of a method for loading a business component according to one or more embodiments.
- Fig. 2 is a schematic flowchart of a method for loading a business component according to one or more embodiments.
- Fig. 3 is a schematic flowchart of obtaining a preset resource pool according to one or more embodiments.
- Fig. 4 is a schematic flowchart of obtaining a preset resource pool in another embodiment.
- Fig. 5 is a schematic diagram of a process of generating a business component interface document according to one or more embodiments.
- Fig. 6 is a schematic diagram of a process of obtaining business component status information according to one or more embodiments.
- Fig. 7 is a schematic flowchart of updating business components in a preset resource pool according to one or more embodiments.
- Fig. 8 is a block diagram of a service component loading apparatus according to one or more embodiments.
- Figure 9 is a block diagram of a computer device according to one or more embodiments.
- the service component loading method provided in this application can be applied to the application environment as shown in FIG. 1.
- the terminal 102 communicates with the server 104 through the network.
- the server 104 receives the service component loading instruction sent by the terminal 102, the calling instruction carries the caller identification and the component identification, and searches the caller identification in the preset permission table according to the loading instruction; when the server 104 finds the calling party in the preset permission table When the party identifier is used, the callable component identifier corresponding to the caller identifier is obtained; when the component identifier exists in the callable component identifier, the server 104 copies the business component corresponding to the component identifier from the preset resource pool, and returns the business component to the terminal 102 to Make the terminal 102 load the service component.
- the terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
- the server 104 may be implemented by an independent server or a server cluster composed of multiple servers.
- a service component loading method is provided.
- the method is applied to the server in FIG. 1 as an example for description, including the following steps:
- S202 Receive a service component loading instruction, where the calling instruction carries a caller identification and a component identification, and search for the caller identification in a preset permission table according to the loading instruction.
- the preset permission table refers to a data table preset for permission verification.
- the caller ID refers to the user ID who wants to call the business component.
- the component identifier is used to uniquely identify the corresponding business component.
- the server receives the service component loading instruction sent by the terminal, parses the service component loading instruction, and obtains the caller identification and the component identification to be invoked carried by the instruction.
- the server performs authorization verification according to the loading instruction, and verifies whether the caller ID has the authorization to call. That is, look up the caller ID in the preset permission table.
- the callable component identifier refers to the component identifier corresponding to the component that can be called by the verified caller identifier.
- the server when the server can find the caller ID in the preset permission table, it means that the permission verification of the caller ID is passed. At this time, the server obtains the callable component ID corresponding to the caller ID in the preset permission table. . When the server does not find the caller ID in the preset permission table, at this time, the permission verification of the caller ID fails, and the server will return a prompt of no permission to the terminal corresponding to the caller ID.
- the preset resource pool is preset to store component resources, business resources, etc. used by developers in the historical development process.
- the server matches the parsed component identifier in the callable component identifier, and when a consistent component identifier can be matched, it indicates that the component identifier exists in the callable component identifier.
- the server copies the business component corresponding to the component identifier in the preset resource pool according to the component identifier, and the server returns the obtained business component to the terminal corresponding to the caller identifier.
- the terminal receives the business component sent by the server, it loads the service Component into the business process to complete the development of the project.
- developers can obtain multiple business components in the preset resource pool, combine the multiple business components to generate a business component set that meets the current development business, and load the business component set to reduce development Time, complete development tasks faster.
- the calling instruction carries the caller identification and the component identification, and the caller identification is searched in the preset permission table according to the loading instruction, and when the caller identification is found in the preset permission table When, obtain the callable component ID corresponding to the caller ID.
- the business component corresponding to the component identifier is copied from the preset resource pool, and the business component is returned to the terminal, so that the terminal loads the business component.
- the calling instruction before step S202, that is, before receiving the service component loading instruction, the calling instruction carries the caller identification and the component identification, and the caller identification is searched in the preset permission table according to the loading instruction Before, it also includes steps:
- S302 Obtain business scenario information, and obtain corresponding business realization logic information according to the business scenario information.
- Business scenario information refers to the information needed when the business is to be developed in the corresponding use scenario. For example, to develop a button, the size of the button is different in different business scenarios. Get the size of the button in the business scenario to be developed.
- the business realization logic information refers to the logic code that realizes the business function.
- the business scenario information is obtained, and the corresponding business realization logic information is obtained according to the business scenario information.
- the additional loan business information is obtained, and the additional loan business realization logic code is obtained according to the additional loan business information.
- S304 Receive the command line execution instruction, parse the command line according to the command line execution instruction, generate a business component file according to the analysis result, write the business implementation logic into the business component file, and obtain the business component.
- the command line is received through the command line tool, and the command line is used to execute the component generation command.
- the server receives the command line execution instruction, and obtains the pass code file of the service component according to the parsed command line, and obtains the service component file. Then write the business realization logic code into the business component file to obtain the business component. For example, generating additional loan business components through the command line.
- a business component containing multiple business scenario interfaces can be generated, and the business implementation logic codes in different business scenarios can be encapsulated by acquiring the business implementation logic codes in different business scenarios and provide the scenario interfaces corresponding to the business scenarios. . When it needs to be used, by obtaining the scene interface corresponding to the business scene, and calling the business component through the scene interface, it can be used directly, which is convenient and fast.
- S306 Generate a component identifier, associate the component identifier with the business component and write it into the resource pool to obtain a preset resource pool.
- the component identifier is generated, and the component identifier and the business component are associated and written into the resource pool.
- the developer obtains the preset resource pool by writing different business components into the resource pool during the historical development process.
- step S306 which is to generate a component identifier, associate the component identifier and the business component into the resource pool, and obtain the preset resource pool, includes the steps:
- S402 Acquire the number of invocations of the business component, and when the number of invocations is greater than the preset number, generate a component identifier corresponding to the business component.
- the server obtains the number of invocations of the business component from the invocation log of the business component, and when the number of invocations of the business component is greater than the preset number of times, generates a component identification corresponding to the business component.
- the extended interface is used to write the business components that meet the requirements into the resource pool.
- the server associates the component identifier and the service component into the resource pool through the extended interface to obtain the preset resource pool.
- the from component which encapsulates the verification business logic based on common ID verification in loan business. This component is required in different loan scenarios. Then the number of invocations of the component is greater than the preset number of times, and the from component is added to the resource pool, which is convenient for subsequent developers to use.
- the number of invocations of the business component is obtained, and when the number of invocations is greater than the preset number, the component identification corresponding to the business component is generated, and the component identification and the business component are associated and written into the resource pool through the extension interface to obtain the preset resource Pool, can write highly reused business components into the resource pool, save the space resources of the resource pool, and facilitate subsequent use.
- step S306 that is, after the component identification is generated, the component identification and the business component are associated and written into the preset resource pool.
- the method further includes the following steps:
- S502 Receive a document command line execution instruction, parse the document command line according to the document command line execution instruction, and obtain interface information of each business component in the resource pool according to the parsing result.
- the interface information refers to the specific information of the business component interface, including interface name, interface request parameters, interface calling method, interface return field, and so on.
- the server receives the document command line execution instruction, parses the document command line according to the document command line execution instruction, and obtains the interface information of each business component in the resource pool according to the analysis result.
- S504 Obtain a preset interface document template, write the interface information of each business component into the preset interface document template, and generate a business component interface document.
- the preset interface document template refers to the interface document template set in the server in advance.
- the server obtains a preset interface document template, writes the obtained interface information of each business component into the preset interface document template, and generates a business component interface document.
- the document command line is parsed according to the document command line execution instruction, the interface information of each business component in the resource pool is obtained according to the analysis result, the server obtains the preset interface document template, and The obtained interface information of each business component is written into a preset interface document template to generate a business component interface document, which is convenient for subsequent developers to view the business component interface document during development, so as to call the business component.
- step S206 that is, when the component identifier exists in the callable component identifier, the business component corresponding to the component identifier is copied from the preset resource pool, and the business component is returned to the terminal, so that The terminal loads business components, including steps:
- the status information of a business component refers to the current state of the business component in the resource pool, including callable and uncallable.
- the server obtains the status information of the business component corresponding to the component identifier in the preset resource pool.
- the business component corresponding to the component identifier is found from the preset resource pool, and the status information corresponding to the business component is obtained.
- S604 When the state information of the service component is in a callable state, copy the service component corresponding to the component identifier from the preset resource pool, and return the service component to the terminal, so that the terminal loads the service component.
- the server detects that the status information of the service component is in a callable state
- the service component corresponding to the component identifier is copied from the preset resource pool, and the service component is returned to the terminal, so that the terminal loads the service component.
- the server detects that the status information of the service component is in an unavailable state, it returns a prompt to the terminal that the service component is unavailable.
- the status information of the business component corresponding to the component identifier in the preset resource pool is obtained.
- the status information of the business component is in the callable state, the status information is obtained from the preset resource pool. Copy the business component corresponding to the component identifier in the middle, and return the business component to the terminal so that the terminal loads the business component.
- step S206 that is, when the component identifier exists in the callable component identifier, the business component corresponding to the component identifier is copied from the preset resource pool, and the business component is returned to the terminal, After the terminal loads the business components, it also includes steps:
- S702 Receive a business component update instruction, where the update instruction carries a target component identifier, and obtain the updated business component according to the business component update instruction.
- the target component identifier refers to the component identifier of the business component that needs to be updated.
- the server receives the business component update instruction, the update instruction carries the target component identifier, and obtains the updated business component according to the business component update instruction.
- S704 Search for the target business component corresponding to the target component identifier in the preset resource pool, and replace the target business component with the updated business component.
- the target business component refers to the business component to be updated in the bathroom resource pool.
- the server searches for the target business component corresponding to the target component identifier in the preset resource pool, and replaces the target business component with the updated business component. That is, the target business component is deleted from the preset resource pool, and then the updated business component is written into the preset resource pool. Or, use the incremental update method to update the target business component, that is, obtain the content of the target business component that needs to be updated, and replace the part of the content with the updated content to obtain the updated business component.
- S706 Obtain the target caller identifier of the calling target service component, and send the updated service component to the terminal corresponding to the target caller identifier, so that the terminal corresponding to the target caller identifier replaces the target service component with the updated service component.
- the target caller ID refers to the caller ID corresponding to the target business component.
- the server obtains the target caller ID of the calling target service component, and sends the updated service component to the terminal corresponding to the target caller ID.
- the terminal receives the updated service component sent by the server and replaces the target service component with the updated service component.
- the update instruction carries the target component identifier
- the updated business component is obtained according to the business component update instruction
- the target business component corresponding to the target component identifier is searched in the preset resource pool
- the The target business component is replaced with the updated business component.
- Obtain the target caller ID of the calling target business component and send the updated business component to the terminal corresponding to the target caller ID, so that the terminal corresponding to the target caller ID replaces the target business component with the updated business component, which can be updated in time
- the business components of the preset resource pool are convenient to optimize the business components and facilitate subsequent developers to use.
- a service component loading apparatus 800 including: an identification search module 802, a component identification acquisition module 804, and a component loading module 806, wherein:
- the identification search module 802 is used to receive a service component loading instruction, the calling instruction carries the caller identification and the component identification, and the caller identification is searched in the preset permission table according to the loading instruction;
- the component identification obtaining module 804 is configured to obtain the callable component identification corresponding to the caller identification when the caller identification is found in the preset permission table;
- the component loading module 806 is used to copy the business component corresponding to the component identification from the preset resource pool when the component identification exists in the callable component identification, and return the business component to the terminal so that the terminal loads the business component.
- the service component loading device 800 further includes:
- the information obtaining module is used to obtain business scenario information, and obtain corresponding business realization logic information according to the business scenario information;
- the component acquisition module is used to receive command line execution instructions, parse the command line according to the command line execution instructions, generate a business component file according to the analysis result, write the business realization logic into the business component file to obtain the business component;
- the resource pool obtaining module is used to generate the component identifier, associate the component identifier and the business component into the resource pool, and obtain the preset resource pool.
- the resource pool obtaining module includes:
- the frequency acquisition unit is used to acquire the number of invocations of the business component, and when the number of invocations is greater than the preset number, generate a component ID corresponding to the business component;
- the component writing unit is used to associate the component identifier and the business component into the resource pool through the extended interface to obtain the preset resource pool.
- the service component loading device 800 further includes:
- the interface information acquisition module is used to receive the document command line execution instruction, parse the document command line according to the document command line execution instruction, and obtain the interface information of each business component in the resource pool according to the analysis result;
- the document generation module is used to obtain the preset interface document template, write the interface information of each business component into the preset interface document template, and generate the business component interface document.
- the component loading module 806 includes:
- the status obtaining unit is configured to obtain status information of the business component corresponding to the component identifier in the preset resource pool when the component identifier exists in the callable component identifier;
- the component calling unit is used to copy the business component corresponding to the component identifier from the preset resource pool when the state information of the business component is in a callable state, and return the business component to the terminal so that the terminal loads the business component.
- the service component loading device 800 further includes:
- the update instruction receiving module is used to receive the business component update instruction, the update instruction carries the target component identifier, and the updated business component is obtained according to the business component update instruction;
- the update module is used to find the target business component corresponding to the target component identifier in the preset resource pool, and replace the target business component with the updated business component;
- the component sending module is used to obtain the target caller ID of the calling target business component, and send the updated business component to the terminal corresponding to the target caller ID, so that the terminal corresponding to the target caller ID replaces the target business component with the updated Business components.
- Each module in the above-mentioned service component loading device can be implemented in whole or in part by software, hardware and a combination thereof.
- the foregoing modules may be embedded in the form of hardware or independent of the processor in the computer device, or may be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the foregoing modules.
- a computer device is provided.
- the computer device may be a server, and its internal structure diagram may be as shown in FIG. 9.
- the computer equipment includes a processor, a memory, a network interface and a database connected through a system bus.
- the processor of the computer device is used to provide calculation and control capabilities.
- the memory of the computer device includes a non-volatile storage medium and an internal memory.
- the non-volatile storage medium stores an operating system, computer readable instructions, and a database.
- the internal memory provides an environment for the operation of the operating system and computer-readable instructions in the non-volatile storage medium.
- the database of the computer equipment is used to store business component data.
- the network interface of the computer device is used to communicate with an external terminal through a network connection.
- the computer-readable instruction is executed by the processor to implement a service component loading method.
- FIG. 9 is only a block diagram of part of the structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied.
- the specific computer equipment may Including more or fewer parts than shown in the figure, or combining some parts, or having a different arrangement of parts.
- a computer device includes a memory and one or more processors.
- the memory stores computer readable instructions.
- the steps of the service component loading method provided in any embodiment of the present application are implemented.
- One or more non-volatile storage media storing computer-readable instructions.
- the one or more processors implement the services provided in any embodiment of the present application The steps of the component loading method.
- Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
- ROM read only memory
- PROM programmable ROM
- EPROM electrically programmable ROM
- EEPROM electrically erasable programmable ROM
- Volatile memory may include random access memory (RAM) or external cache memory.
- RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
一种业务组件加载方法，包括：接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识；当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识；当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
Description
相关申请的交叉引用
本申请要求于2019年04月04日提交中国专利局，申请号为2019102715514，申请名称为“业务组件加载方法、装置、计算机设备和存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请涉及一种业务组件加载方法、装置、计算机设备和存储介质。
随着互联网技术的飞速发展，企业在进行业务项目开发时，通过使用开源组件来进行开发，以节省企业成本。但是，开发人员在使用开源组件时，通常都需要根据企业业务项目的需求来对开源组件进行调整，甚至，会深入理解源码进行进一步的调整。经过调整之后的开源组件才能在企业业务项目中进行加载使用。但是，由于，开源组件的业务逻辑复杂，对开源组件重新进行调整，增加了业务开发时间，影响企业业务项目的开发效率。
发明内容
根据本申请公开的各种实施例，提供一种业务组件加载方法、装置、计算机设备和存储介质。
一种业务组件加载方法，包括：
接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识；
当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识；
当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
一种业务组件加载装置，包括：
标识查找模块，用于接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识；
组件标识获取模块，用于当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识；及
组件加载模块，用于当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
一种计算机设备，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行以下步骤：
接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识；
当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识；及
当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识；
当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识；及
当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中业务组件加载方法的应用场景图。
图2为根据一个或多个实施例中业务组件加载方法的流程示意图。
图3为根据一个或多个实施例中得到预设资源池的流程示意图。
图4为另一个实施例中得到预设资源池的流程示意图。
图5为根据一个或多个实施例中生成业务组件接口文档的流程示意图。
图6为根据一个或多个实施例中获取业务组件状态信息的流程示意图。
图7为根据一个或多个实施例中更新预设资源池中业务组件的流程示意图。
图8为根据一个或多个实施例中业务组件加载装置的框图。
图9为根据一个或多个实施例中计算机设备的框图。
为了使本申请的技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供的业务组件加载方法，可以应用于如图1所示的应用环境中。终端102通过网络与服务器104进行通信。服务器104接收到终端102发送的业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识；当服务器104在预设权限表中查找到调 用方标识时，获取调用方标识对应的可调用组件标识；当可调用组件标识中存在组件标识时，服务器104从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端102，以使终端102加载业务组件。终端102可以但不限于是各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备，服务器104可以用独立的服务器或者是多个服务器组成的服务器集群来实现。
在其中一个实施例中，如图2所示，提供了一种业务组件加载方法，以该方法应用于图1中的服务器为例进行说明，包括以下步骤：
S202，接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识。
预设权限表是指预先设置好的用于进行权限验证的数据表。调用方标识是指要调用业务组件的用户标识。组件标识用于唯一标识对应的业务组件。
具体地，服务器接收到终端发送的业务组件加载指令，解析该业务组件加载指令，得到该指令携带的调用方标识和要调用的组件标识。服务器根据该加载指令进行权限验证，验证调用方标识是否有权限进行调用。即在预先设置好的权限表中查找该调用方标识。
S204，当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识。
可调用组件标识是指通过验证的调用方标识可以进行调用的组件对应的组件标识。
具体地，当服务器能够在预设权限表中查找到调用方标识时，说明对该调用方标识的权限验证通过，此时，服务器在预设权限表中获取调用方标识对应的可调用组件标识。当服务器未在预设权限表中查找到调用方标识，此时，该调用方标识的权限验证未通过，此时服务器会向调用方标识对应的终端返回没有权限的提示。
S206，当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
预设资源池是预先设置好的用于存储开发人员在历史开发过程中使用过的组件资源、业务资源等等。
具体地，服务器在可调用组件标识中匹配解析得到的组件标识，当能够匹配到一致的组件标识时，说明该可调用组件标识中存在组件标识。此时，服务器根据该组件标识在预设资源池中复制该组件标识对应的业务组件，服务器将得到的业务组件返回调用方标识对应的终端，终端接收到服务器发送的业务组件时，加载该业务组件到业务流程中，以完成项目的开发。在一个实施例中，开发人员可以获取到预设资源池中的多个业务组件，将该多个业务组件进行组合，生成符合当前开发业务的业务组件集，加载该业务组件集，能够减少开发时间，更快完成开发任务。
上述业务组件加载方法，通过接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识，当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识。当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。开发人员在进行业务项目开发时，通过从预设资源池中得到对应的业务组件，然后在终端进行加载该业务组件，能够直接使用该业务组件，提高了业务项目的开发效率。
在其中一个实施例中，如图3所示，在步骤S202之前，即在接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识之前，还包括步骤：
S302，获取业务场景信息，根据业务场景信息得到对应的业务实现逻辑信息。
业务场景信息是指该业务在对应的使用场景下要进行开发时需要的信息，比如要开发一个按钮，该按钮在不同的业务场景下的大小是不同的。获取到该按钮的在要开发的业务场景下的大小。业务实现逻辑信息是指实现该业务功能的逻辑代码。
具体地，获取到业务场景信息，根据业务场景信息得到对应的业务实现逻辑信息。比如贷款业务中的追加贷，获取该追加贷业务信息，根据该追加贷业务信息得到追加贷业务实现逻辑代码。
S304，接收命令行执行指令，根据命令行执行指令解析命令行，根据解析结果生成业务组件文件，将业务实现逻辑写入业务组件文件中，得到业务组件。
具体地，通过命令行工具接收到命令行，该命令行用于执行组件生成命令。服务器接收到该命令行执行指令，根据解析命令行，得到该业务组件的通过代码文件，得到业务组件文件。然后将业务实现逻辑代码写入该业务组件文件中，得到业务组件。比如，通过命令行生成追加贷业务组件。在一个实施例中可以生成包含多个业务场景接口的业务组件，通过获取的不同业务场景下业务的实现逻辑代码，将各个不同场景下的业务实现逻辑代码进行封装并提供业务场景对应的场景接口。当需要使用时，通过获取业务场景对应的场景接口，通过该场景接口调用该业务组件，就可以直接进行使用，方便快捷。
S306，生成组件标识，将组件标识和业务组件关联写入资源池中，得到预设资源池。
具体地，生成组件标识，将组件标识和业务组件关联写入资源池中，开发人员通过在历史开发过程中将不同的业务组件写入资源池中，就得到了预设资源池。
在上述实施例中，通过获取业务场景信息，根据业务场景信息得到对应的业务实现逻辑信息，接收命令行执行指令，根据命令行执行指令解析命令行，根据解析结果生成业务组件文件，将业务实现逻辑写入业务组件文件中，得到业务组件。生成组件标识，将组件标识和业务组件关联写入资源池中，得到预设资源池。通过开发人员在历史开发过程中积累业务组件，将业务组件写入资源池中，得到预设资源池，方便后续开发人员进行使用，提高后续开发人员的开发效率，降低开发门槛。
在其中一个实施例中，如图4所示，步骤S306，即生成组件标识，将组件标识和业务组件关联写入资源池中，得到预设资源池，包括步骤：
S402，获取业务组件的调用次数，当调用次数大于预设次数时，生成业务组件对应的组件标识。
具体地，服务器通过业务组件的调用日志获取业务组件的调用次数，当该业务组件的调用次数大于预设次数时，生成该业务组件对应的组件标识。
S404，将组件标识和业务组件通过扩展接口关联写入资源池中，得到预设资源池。
扩展接口用于将符合要求的业务组件写入资源池。
具体地，服务器将组件标识和业务组件通过扩展接口关联写入资源池中，得到预设资源池。例如：from组件，该组件封装了基于贷款业务常见的身份证号验证等校验业务逻辑。在不同的贷款场景中都需要使用该组件。则该组件的调用次数大于预设次数，将该from组件添加到资源池中，便于后续开发人员的使用。
通过上述实施例中，获取业务组件的调用次数，当调用次数大于预设次数时，生成业务组件对应的组件标识，将组件标识和业务组件通过扩展接口关联写入资源池中，得到预设资源池，可以将高复用的业务组件写入资源池中，节省资源池空间资源，且方便后续使用。
在其中一个实施例中，如图5所示，在步骤S306之后，即在生成组件标识，将组件标识和业务组件关联写入预设资源池中，得到预设资源池之后，还包括步骤：
S502，接收文档命令行执行指令，根据文档命令行执行指令解析文档命令行，根据解析结果获取资源池中各个业务组件的接口信息。
其中，接口信息是指该业务组件接口的具体信息，包括接口名称、接口请求参数、接口调用方法和接口返回字段等等。
具体地，服务器接收到文档命令行执行指令，根据文档命令行执行指令解析文档命令行，根据解析结果获取资源池中各个业务组件的接口信息。
S504，获取预设接口文档模板，将各个业务组件的接口信息写入预设接口文档模板中，生成业务组件接口文档。
预设接口文档模板是指预先在服务器中设置好接口文档模板。
具体地，服务器获取预先设置好的接口文档模板，将得到的各个业务组件的接口信息写入预设接口文档模板中，生成业务组件接口文档。
在上述实施例中，通过接收文档命令行执行指令，根据文档命令行执行指令解析文档命令行，根据解析结果获取资源池中各个业务组件的接口信息，服务器获取预先设置好的接口文档模板，将得到的各个业务组件的接口信息写入预设接口文档模板中，生成业务组件接口文档，便于后续开发人员在进行开发时查看业务组件接口文档，从而调用业务组件。
在其中一个实施例中，如图6所示，步骤S206，即当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件，包括步骤：
S602，当可调用组件标识中存在组件标识时，获取预设资源池中组件标识对应的业务组件的状态信息。
其中，业务组件的状态信息是指该业务组件在资源池中当前的状态，包括可调用和不可调用。
具体地，当可调用组件标识中存在组件标识时，服务器获取预设资源池中组件标识对应的业务组件的状态信息。从预设资源池中查找到组件标识对应的业务组件，获取到业务组件对应的状态信息。
S604，当业务组件的状态信息为可调用状态时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
具体地，当服务器检测到该业务组件的状态信息为可调用状态时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。当服务器检测到该业务组件的状态信息为不可调用状态时，向终端返回该业务组件不可用的提示。
在上述实施例中，当可调用组件标识中存在组件标识时，获取预设资源 池中组件标识对应的业务组件的状态信息，当业务组件的状态信息为可调用状态时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
在其中一个实施例中，如图7所示，在步骤S206之后，即当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件之后，还包括步骤：
S702，接收业务组件更新指令，更新指令携带有目标组件标识，根据业务组件更新指令获取更新后的业务组件。
其中，目标组件标识是指需要进行更新的业务组件的组件标识。
具体地，服务器接收业务组件更新指令，该更新指令携带有目标组件标识，根据业务组件更新指令获取更新后的业务组件。
S704，在预设资源池中查找目标组件标识对应的目标业务组件，将目标业务组件替换为更新后的业务组件。
目标业务组件是指在浴室资源池中待更新的业务组件。
具体地，服务器在预设资源池中查找目标组件标识对应的目标业务组件，将目标业务组件替换为更新后的业务组件。即将目标业务组件从预设资源池中删除，然后将更新后的业务组件写入预设资源池中。或者，使用增量更新的方法对目标业务组件进行更新，即获取到目标业务组件需要更新的内容，将该部分的内容替换为更新后的内容，得到更新后的业务组件。
S706，获取调用目标业务组件的目标调用方标识，向目标调用方标识对应的终端发送更新后的业务组件，以使目标调用方标识对应的终端将目标业务组件替换为更新后的业务组件。
目标调用方标识是指目标业务组件对应的调用方的标识。
具体地，服务器获取调用目标业务组件的目标调用方标识，向目标调用方标识对应的终端发送更新后的业务组件，终端接收到服务器发送的更新后的业务组件，将目标业务组件替换为更新后的业务组件。
在上述实施例中，通过接收业务组件更新指令，更新指令携带有目标组 件标识，根据业务组件更新指令获取更新后的业务组件，在预设资源池中查找目标组件标识对应的目标业务组件，将目标业务组件替换为更新后的业务组件。获取调用目标业务组件的目标调用方标识，向目标调用方标识对应的终端发送更新后的业务组件，以使目标调用方标识对应的终端将目标业务组件替换为更新后的业务组件，能够及时更新预设资源池的业务组件，便于对业务组件进行优化，方便后续开发人员使用。
应该理解的是，虽然图2-7的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2-7中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
在其中一个实施例中，如图8所示，提供了一种业务组件加载装置800，包括：标识查找模块802、组件标识获取模块804和组件加载模块806，其中：
标识查找模块802，用于接收业务组件加载指令，调用指令携带有调用方标识和组件标识，根据加载指令在预设权限表中查找调用方标识；
组件标识获取模块804，用于当在预设权限表中查找到调用方标识时，获取调用方标识对应的可调用组件标识；
组件加载模块806，用于当可调用组件标识中存在组件标识时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
在其中一个实施例中，业务组件加载装置800，还包括：
信息得到模块，用于获取业务场景信息，根据业务场景信息得到对应的业务实现逻辑信息；
组件得到模块，用于接收命令行执行指令，根据命令行执行指令解析命 令行，根据解析结果生成业务组件文件，将业务实现逻辑写入业务组件文件中，得到业务组件；
资源池得到模块，用于生成组件标识，将组件标识和业务组件关联写入资源池中，得到预设资源池。
在其中一个实施例中，资源池得到模块，包括：
次数获取单元，用于获取业务组件的调用次数，当调用次数大于预设次数时，生成业务组件对应的组件标识；
组件写入单元，用于将组件标识和业务组件通过扩展接口关联写入资源池中，得到预设资源池。
在其中一个实施例中，业务组件加载装置800，还包括：
接口信息获取模块，用于接收文档命令行执行指令，根据文档命令行执行指令解析文档命令行，根据解析结果获取资源池中各个业务组件的接口信息；
文档生成模块，用于获取预设接口文档模板，将各个业务组件的接口信息写入预设接口文档模板中，生成业务组件接口文档。
在其中一个实施例中，组件加载模块806，包括：
状态获取单元，用于当可调用组件标识中存在组件标识时，获取预设资源池中组件标识对应的业务组件的状态信息；
组件调用单元，用于当业务组件的状态信息为可调用状态时，从预设资源池中复制组件标识对应的业务组件，将业务组件返回终端，以使终端加载业务组件。
在其中一个实施例中，业务组件加载装置800，还包括：
更新指令接收模块，用于接收业务组件更新指令，更新指令携带有目标组件标识，根据业务组件更新指令获取更新后的业务组件；
更新模块，用于在预设资源池中查找目标组件标识对应的目标业务组件，将目标业务组件替换为更新后的业务组件；
组件发送模块，用于获取调用目标业务组件的目标调用方标识，向目标 调用方标识对应的终端发送更新后的业务组件，以使目标调用方标识对应的终端将目标业务组件替换为更新后的业务组件。
关于业务组件加载装置的具体限定可以参见上文中对于业务组件加载方法的限定，在此不再赘述。上述业务组件加载装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是服务器，其内部结构图可以如图9所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口和数据库。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机可读指令和数据库。该内存储器为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。该计算机设备的数据库用于存储业务组件数据。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读指令被处理器执行时以实现一种业务组件加载方法。
本领域技术人员可以理解，图9中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
一种计算机设备，包括存储器和一个或多个处理器，存储器中存储有计算机可读指令，计算机可读指令被处理器执行时实现本申请任意一个实施例中提供的业务组件加载方法的步骤。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器实现本申请任意一个实施例中提供的业务组件加载方法的步骤。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。
Claims (20)
- 一种业务组件加载方法，包括：接收业务组件加载指令，所述调用指令携带有调用方标识和至少两个组件标识，根据所述调用指令在预设权限表中查找所述调用方标识；当在所述预设权限表中查找到所述调用方标识时，获取调用方标识对应的各个可调用组件标识；及当所述各个可调用组件标识中存在所述至少两个组件标识时，从预设资源池中复制所述至少两个组件标识对应的至少两个业务组件，将所述至少两个业务组件进行组合，生成业务组件集，将所述业务组件集返回终端，以使所述终端加载所述业务组件集。
- 根据权利要求1所述的方法，其特征在于，在所述接收业务组件加载指令，所述调用指令携带有调用方标识和至少两个组件标识，根据所述调用指令在预设权限表中查找所述调用方标识之前，还包括：获取业务场景信息，根据所述业务场景信息得到对应的业务实现逻辑信息；接收命令行执行指令，根据所述命令行执行指令解析所述命令行，根据所述解析结果生成业务组件文件，将所述业务实现逻辑写入所述业务组件文件中，得到业务组件；及生成组件标识，将所述组件标识和所述业务组件关联写入资源池中，得到所述预设资源池。
- 根据权利要求2所述的方法，其特征在于，所述生成组件标识，将所述组件标识和所述业务组件关联写入资源池中，得到所述预设资源池，包括：获取所述业务组件的调用次数，当所述调用次数大于预设次数时，生成所述业务组件对应的组件标识；及将所述组件标识和所述业务组件通过扩展接口关联写入资源池中，所述预设资源池。
- 根据权利要求2所述的方法，其特征在于，在所述生成组件标识，将 所述组件标识和所述业务组件关联写入预设资源池中，得到预设资源池之后，还包括：接收文档命令行执行指令，根据所述文档命令行执行指令解析所述文档命令行，根据解析结果获取所述资源池中各个业务组件的接口信息；及获取预设接口文档模板，将所述各个业务组件的接口信息写入所述预设接口文档模板中，生成业务组件接口文档。
- 根据权利要求1所述的方法，其特征在于，当所述各个可调用组件标识中存在所述至少两个组件标识时，从预设资源池中复制所述至少两个组件标识对应的至少两个业务组件，将所述至少两个业务组件进行组合，生成业务组件集，将所述业务组件集返回终端，以使所述终端加载所述业务组件集，包括：当所述可调用组件标识中存在所述组件标识时，获取预设资源池中所述组件标识对应的业务组件的状态信息；及当所述业务组件的状态信息为可调用状态时，从预设资源池中复制所述组件标识对应的业务组件，将所述业务组件返回终端，以使所述终端加载所述业务组件。
- 根据权利要求1所述的方法，其特征在于，所述当所述各个可调用组件标识中存在所述至少两个组件标识时，从预设资源池中复制所述至少两个组件标识对应的至少两个业务组件，将所述至少两个业务组件进行组合，生成业务组件集，将所述业务组件集返回终端，以使所述终端加载所述业务组件集之后，还包括：接收业务组件更新指令，所述更新指令携带有目标组件标识，根据所述业务组件更新指令获取更新后的业务组件；在所述预设资源池中查找所述目标组件标识对应的目标业务组件，将所述目标业务组件替换为更新后的业务组件；及获取调用所述目标业务组件的目标调用方标识，向所述目标调用方标识对应的终端发送所述更新后的业务组件，以使所述目标调用方标识对应的终 端将目标业务组件替换为更新后的业务组件。
- 一种业务组件加载装置，包括：标识查找模块，用于接收业务组件加载指令，所述调用指令携带有调用方标识和至少两个组件标识，根据所述调用指令在预设权限表中查找所述调用方标识；组件标识获取模块，用于当在所述预设权限表中查找到所述调用方标识时，获取调用方标识对应的各个可调用组件标识；组件加载模块，用于当所述各个可调用组件标识中存在所述至少两个组件标识时，从预设资源池中复制所述至少两个组件标识对应的至少两个业务组件，将所述至少两个业务组件进行组合，生成业务组件集，将所述业务组件集返回终端，以使所述终端加载所述业务组件集。
- 根据权利要求7所述的装置，其特征在于，所述业务组件加载装置，还包括：信息得到模块，用于获取业务场景信息，根据所述业务场景信息得到对应的业务实现逻辑信息；组件得到模块，用于接收命令行执行指令，根据所述命令行执行指令解析所述命令行，根据所述解析结果生成业务组件文件，将所述业务实现逻辑写入所述业务组件文件中，得到业务组件；资源池得到模块，用于生成组件标识，将所述组件标识和所述业务组件关联写入资源池中，得到所述预设资源池。
- 根据权利要求8所述的装置，其特征在于，所述资源池得到模块，包括：次数获取单元，用于获取所述业务组件的调用次数，当所述调用次数大于预设次数时，生成所述业务组件对应的组件标识；及组件写入单元，用于将所述组件标识和所述业务组件通过扩展接口关联写入资源池中，所述预设资源池。
- 根据权利要求7所述的装置，其特征在于，所述业务组件加载装置， 还包括：接口信息获取模块，用于接收文档命令行执行指令，根据所述文档命令行执行指令解析所述文档命令行，根据解析结果获取所述资源池中各个业务组件的接口信息；及文档生成模块，用于获取预设接口文档模板，将所述各个业务组件的接口信息写入所述预设接口文档模板中，生成业务组件接口文档。
- 一种计算机设备，包括存储器及一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：接收业务组件加载指令，所述调用指令携带有调用方标识和至少两个组件标识，根据所述调用指令在预设权限表中查找所述调用方标识；当在所述预设权限表中查找到所述调用方标识时，获取调用方标识对应的各个可调用组件标识；当所述各个可调用组件标识中存在所述至少两个组件标识时，从预设资源池中复制所述至少两个组件标识对应的至少两个业务组件，将所述至少两个业务组件进行组合，生成业务组件集，将所述业务组件集返回终端，以使所述终端加载所述业务组件集。
- 根据权利要求11所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：获取业务场景信息，根据所述业务场景信息得到对应的业务实现逻辑信息；接收命令行执行指令，根据所述命令行执行指令解析所述命令行，根据所述解析结果生成业务组件文件，将所述业务实现逻辑写入所述业务组件文件中，得到业务组件；生成组件标识，将所述组件标识和所述业务组件关联写入资源池中，得到所述预设资源池。
- 根据权利要求12所述的计算机设备，其特征在于，所述处理器执行 所述计算机可读指令时还执行以下步骤：获取所述业务组件的调用次数，当所述调用次数大于预设次数时，生成所述业务组件对应的组件标识；将所述组件标识和所述业务组件通过扩展接口关联写入资源池中，所述预设资源池。
- 根据权利要求12所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：接收文档命令行执行指令，根据所述文档命令行执行指令解析所述文档命令行，根据解析结果获取所述资源池中各个业务组件的接口信息；获取预设接口文档模板，将所述各个业务组件的接口信息写入所述预设接口文档模板中，生成业务组件接口文档。
- 根据权利要求11所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：当所述可调用组件标识中存在所述组件标识时，获取预设资源池中所述组件标识对应的业务组件的状态信息；当所述业务组件的状态信息为可调用状态时，从预设资源池中复制所述组件标识对应的业务组件，将所述业务组件返回终端，以使所述终端加载所述业务组件。
- 一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：接收业务组件加载指令，所述调用指令携带有调用方标识和至少两个组件标识，根据所述调用指令在预设权限表中查找所述调用方标识；当在所述预设权限表中查找到所述调用方标识时，获取调用方标识对应的各个可调用组件标识；当所述各个可调用组件标识中存在所述至少两个组件标识时，从预设资源池中复制所述至少两个组件标识对应的至少两个业务组件，将所述至少两 个业务组件进行组合，生成业务组件集，将所述业务组件集返回终端，以使所述终端加载所述业务组件集。
- 根据权利要求16所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：获取业务场景信息，根据所述业务场景信息得到对应的业务实现逻辑信息；接收命令行执行指令，根据所述命令行执行指令解析所述命令行，根据所述解析结果生成业务组件文件，将所述业务实现逻辑写入所述业务组件文件中，得到业务组件；生成组件标识，将所述组件标识和所述业务组件关联写入资源池中，得到所述预设资源池。
- 根据权利要求17所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：获取所述业务组件的调用次数，当所述调用次数大于预设次数时，生成所述业务组件对应的组件标识；将所述组件标识和所述业务组件通过扩展接口关联写入资源池中，所述预设资源池。
- 根据权利要求17所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：接收文档命令行执行指令，根据所述文档命令行执行指令解析所述文档命令行，根据解析结果获取所述资源池中各个业务组件的接口信息；获取预设接口文档模板，将所述各个业务组件的接口信息写入所述预设接口文档模板中，生成业务组件接口文档。
- 根据权利要求16所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：当所述可调用组件标识中存在所述组件标识时，获取预设资源池中所述组件标识对应的业务组件的状态信息；当所述业务组件的状态信息为可调用状态时，从预设资源池中复制所述组件标识对应的业务组件，将所述业务组件返回终端，以使所述终端加载所述业务组件。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910271551.4A CN110109712A (zh) | 2019-04-04 | 2019-04-04 | 业务组件加载方法、装置、计算机设备和存储介质 |
| CN201910271551.4 | 2019-04-04 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020199594A1 true WO2020199594A1 (zh) | 2020-10-08 |
Family
ID=67485166
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2019/117330 Ceased WO2020199594A1 (zh) | 2019-04-04 | 2019-11-12 | 业务组件加载方法、装置、计算机设备和存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110109712A (zh) |
| WO (1) | WO2020199594A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113472903A (zh) * | 2021-09-02 | 2021-10-01 | 腾讯科技（深圳）有限公司 | 一种数据处理方法及装置 |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110109712A (zh) * | 2019-04-04 | 2019-08-09 | 平安科技（深圳）有限公司 | 业务组件加载方法、装置、计算机设备和存储介质 |
| CN110543327B (zh) * | 2019-09-06 | 2023-08-01 | 深圳前海环融联易信息科技服务有限公司 | 业务组件复用方法、装置、计算机设备及存储介质 |
| CN111367891A (zh) * | 2020-03-30 | 2020-07-03 | 中国建设银行股份有限公司 | 建模中间数据的调用方法、装置、设备及可读存储介质 |
| CN111752535A (zh) * | 2020-06-29 | 2020-10-09 | 广州华多网络科技有限公司 | Web页面的开发方法、装置、计算机设备和可读存储介质 |
| CN112635034A (zh) * | 2020-12-30 | 2021-04-09 | 微医云(杭州)控股有限公司 | 一种业务权限系统、权限分配方法、电子设备及存储介质 |
| CN114265588B (zh) * | 2021-12-15 | 2025-01-07 | 北京达佳互联信息技术有限公司 | 组件处理方法、装置、电子设备及存储介质 |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040154024A1 (en) * | 2002-12-31 | 2004-08-05 | Rong Chen | Component based user self-definition event mechanism |
| CN102857524A (zh) * | 2011-06-28 | 2013-01-02 | 腾讯科技（深圳）有限公司 | 一种调用组件的方法及装置 |
| CN102930184A (zh) * | 2012-10-19 | 2013-02-13 | 华为技术有限公司 | 一种功能组件加载方法及装置 |
| CN108958730A (zh) * | 2017-08-23 | 2018-12-07 | 北京五八信息技术有限公司 | 应用程序组件共享方法及装置、终端设备及可读存储介质 |
| CN109254765A (zh) * | 2018-08-22 | 2019-01-22 | 平安科技（深圳）有限公司 | 定时任务管理方法、装置、计算机设备及存储介质 |
| CN110109712A (zh) * | 2019-04-04 | 2019-08-09 | 平安科技（深圳）有限公司 | 业务组件加载方法、装置、计算机设备和存储介质 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8423954B2 (en) * | 2006-03-31 | 2013-04-16 | Sap Ag | Interactive container of development components and solutions |
| CN107577459B (zh) * | 2017-08-21 | 2020-11-13 | 杰为软件系统(深圳)有限公司 | 一种基于组件化的拖拽式跨平台应用开发系统及方法 |
| CN108984160B (zh) * | 2018-06-21 | 2022-04-22 | 中国石油集团安全环保技术研究院有限公司 | 基于组件化的信息化快速开发框架系统 |
| CN109039767A (zh) * | 2018-08-29 | 2018-12-18 | 广汉川友机械租赁有限公司 | 一种分布式资源管理与部署平台 |
-
2019
- 2019-04-04 CN CN201910271551.4A patent/CN110109712A/zh active Pending
- 2019-11-12 WO PCT/CN2019/117330 patent/WO2020199594A1/zh not_active Ceased
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040154024A1 (en) * | 2002-12-31 | 2004-08-05 | Rong Chen | Component based user self-definition event mechanism |
| CN102857524A (zh) * | 2011-06-28 | 2013-01-02 | 腾讯科技（深圳）有限公司 | 一种调用组件的方法及装置 |
| CN102930184A (zh) * | 2012-10-19 | 2013-02-13 | 华为技术有限公司 | 一种功能组件加载方法及装置 |
| CN108958730A (zh) * | 2017-08-23 | 2018-12-07 | 北京五八信息技术有限公司 | 应用程序组件共享方法及装置、终端设备及可读存储介质 |
| CN109254765A (zh) * | 2018-08-22 | 2019-01-22 | 平安科技（深圳）有限公司 | 定时任务管理方法、装置、计算机设备及存储介质 |
| CN110109712A (zh) * | 2019-04-04 | 2019-08-09 | 平安科技（深圳）有限公司 | 业务组件加载方法、装置、计算机设备和存储介质 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113472903A (zh) * | 2021-09-02 | 2021-10-01 | 腾讯科技（深圳）有限公司 | 一种数据处理方法及装置 |
| CN113472903B (zh) * | 2021-09-02 | 2021-11-16 | 腾讯科技（深圳）有限公司 | 一种数据处理方法及装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110109712A (zh) | 2019-08-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020199594A1 (zh) | 业务组件加载方法、装置、计算机设备和存储介质 | |
| CN108573371B (zh) | 数据审批方法、装置、计算机设备和存储介质 | |
| CN109814854B (zh) | 项目框架生成方法、装置、计算机设备和存储介质 | |
| CN110008118B (zh) | 页面数据测试方法、装置、计算机设备和存储介质 | |
| WO2020253061A1 (zh) | 页面生成方法、装置、计算机设备和存储介质 | |
| WO2020151333A1 (zh) | 页面加载方法、装置、计算机设备和存储介质 | |
| CN108446116A (zh) | 应用程序页面的生成方法、装置、计算机设备和存储介质 | |
| CN109039751B (zh) | 配置路由的方法、装置、计算机设备和存储介质 | |
| WO2020192134A1 (zh) | 基于Spring MVC的异常处理方法、装置、计算机设备和存储介质 | |
| WO2020192141A1 (zh) | 接口模拟方法、装置、计算机设备和存储介质 | |
| CN110908778B (zh) | 任务部署方法、系统和存储介质 | |
| US12106253B2 (en) | Container management method, apparatus, and device | |
| CN110489421A (zh) | 数据存储方法、装置、计算机可读存储介质和计算机设备 | |
| CN114118971B (zh) | 基于云原生的在线开发方法、装置、设备及存储介质 | |
| WO2020233092A1 (zh) | 智能合约调用方法、装置、设备和存储介质 | |
| CN109361628B (zh) | 报文组装方法、装置、计算机设备和存储介质 | |
| CN112783866A (zh) | 数据读取方法、装置、计算机设备和存储介质 | |
| CN111258565A (zh) | 小程序的生成方法、系统、服务器及存储介质 | |
| CN109766084B (zh) | 支付应用的定制开发方法、装置、计算机设备和存储介质 | |
| CN109144487B (zh) | 进件业务开发方法、装置、计算机设备和存储介质 | |
| CN114281263A (zh) | 容器集群管理系统的存储资源处理方法、系统和设备 | |
| WO2021120628A1 (zh) | 基于区块链的敏感词检测方法、装置、计算机设备和计算机可读存储介质 | |
| CN114567557A (zh) | 报文处理方法、装置、计算机设备和存储介质 | |
| CN115237459A (zh) | 软件开发工具包生成方法、装置、设备、存储介质及产品 | |
| CN111597240A (zh) | 数据导出方法、装置、计算机设备和存储介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19923542 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 19923542 Country of ref document: EP Kind code of ref document: A1 |