WO2020015170A1 - 接口调用方法、装置及计算机可读存储介质 - Google Patents
接口调用方法、装置及计算机可读存储介质 Download PDFInfo
- Publication number
- WO2020015170A1 WO2020015170A1 PCT/CN2018/107724 CN2018107724W WO2020015170A1 WO 2020015170 A1 WO2020015170 A1 WO 2020015170A1 CN 2018107724 W CN2018107724 W CN 2018107724W WO 2020015170 A1 WO2020015170 A1 WO 2020015170A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- interface
- report
- base class
- management system
- dynamic proxy
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
Definitions
- the present application relates to the field of computer technology, and in particular, to an interface calling method, device, and computer-readable storage medium.
- the report management system is used for BI (Business Intelligence) data source management, report management, task management, log management and other functions; the report distribution system is used for querying, downloading, and regularly collecting task data.
- the report management system is a distributed system. When the report delivery system needs to call BI sources, reports, and other data from the report management system, data is obtained through the external interface provided by the report management system.
- the conventional approach is: the report management system provides an interface for external calls through a servlet; the report delivery system calls the interface provided by the report management system through httpclient to return the required data.
- the disadvantage of this method is that when the report delivery system frequently calls multiple interfaces of the report management system, the report management system needs to provide multiple interfaces, and the report delivery system requires frequent writing methods to use httpclient to call the interfaces, resulting in report management.
- the code at the system is redundant, and the processing of interface calls to the report delivery system is inefficient.
- the present application provides an interface calling method, device, and computer-readable storage medium, whose main purpose is to solve the technical problems of code redundancy at the report management system and low processing efficiency for the interface call of the report issuing system.
- an interface calling method which includes:
- the report issuing system obtains path information of a general servlet interface from the report management system;
- the report issuing system determines a method to be called, creates a dynamic proxy base class of the method, and instantiates the dynamic proxy base class;
- the report management system obtains an instantiated dynamic proxy base class through the universal servlet interface, executes the method to be called according to the instantiated dynamic proxy base class, and sends an execution result to the report delivery system.
- the present application further provides an interface calling device, which includes a memory and a processor, where the memory stores an interface calling program that can be run on the processor, and the interface calling program is When the processor executes, the following steps are implemented:
- the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores an interface calling program, and the interface calling program can be executed by one or more processors to implement The following steps:
- the report issuing system obtains the path information of the general servlet interface from the report management system; the report issuing system determines the method to be called, and creates a dynamic proxy base class for the method And instantiate the dynamic proxy base class; call the general servlet interface according to the path information, and send the instantiated dynamic proxy base class to the general servlet interface; the report management system obtains the instantiated dynamic proxy base class through the general servlet interface, and according to the instance The dynamic dynamic proxy base class executes the method to be called, and sends the execution result to the report delivery system.
- the report management system does not need to implement multiple interface methods, but only needs to implement a common servlet interface.
- the report delivery system obtains the path information of the interface, accesses the interface according to the path information, and passes the dynamic proxy.
- the relevant parameters of the specific method to be called are uploaded to the interface, and the method execution result is obtained. It is not necessary to frequently write the HttpClient to call the specific implementation method of the remote interface, which not only simplifies the code, but also improves the processing efficiency of the interface call. .
- FIG. 1 is a schematic flowchart of an interface calling method according to an embodiment of the present application
- FIG. 2 is a schematic diagram of an internal structure of an interface calling device according to an embodiment of the present application.
- FIG. 3 is a schematic diagram of a module of an interface calling program in an interface calling device according to an embodiment of the present application.
- FIG. 1 is a schematic flowchart of an interface calling method according to an embodiment of the present application. The method may be performed by a device, which may be implemented by software and / or hardware.
- the interface calling method includes:
- step S10 the report delivery system obtains path information of a general servlet interface from the report management system.
- the embodiment of the present application mainly includes a report management system and a report delivery system.
- a remote communication connection is established between the report management system and the report delivery system.
- the report management system is mainly used for report BI data source management, report management, and task management. , Log management and other functions.
- the report delivery system is mainly used for querying, downloading, and downloading task data at regular intervals.
- the report management system is a distributed system. When the report delivery system needs to call BI data sources, reports, and other data from the report management system, data is obtained through the external interface provided by the report management system.
- the report management system is configured with a general servlet interface and an interface configuration file; the corresponding servlet requests corresponding path information through the interface configuration file.
- the path information is mainly used for table delivery.
- the report management system can be found when calling the interface method of the remote report management system.
- a general dynamic proxy processing method The report delivery system searches for the corresponding general servlet interface according to the path information of the exposed interface. Among them, the report management system may actively send the interface configuration file to the report delivery system, and the report delivery system obtains path information from the file.
- the step of the report issuing system obtaining path information of the general servlet interface from the report management system includes: the report issuing system sends an interface information acquisition request to the report management system; the report The management system issues the interface configuration file to the report distribution system according to the interface information acquisition request; the report distribution system obtains the path of the general servlet interface of the report management system according to the interface configuration file information.
- the report delivery system accesses the configuration file of the general servlet interface of the report management system through httpclient to obtain the path information of the general servlet interface, and calls the servlet method of the report management system through the path information.
- the common servlet interface set by the report management system it can be understood as the proxy of the interface.
- the specific method of the remote server can be called on the report delivery system through the reflection mechanism.
- the remote server returns the result data of the execution of the specific method to the report delivery system.
- Step S20 The report delivery system determines a method to be called, creates a dynamic proxy base class for the method, and instantiates the dynamic proxy base class.
- Step S30 Call the universal servlet interface according to the path information, and send the instantiated dynamic proxy base class to the universal servlet interface.
- the report issuing system determines a method to be called, creates a dynamic proxy base class of the method, and instantiates the dynamic proxy base class.
- the steps include: the report issuing system determines a method to be called; and creating the method. Add a pre-created custom annotation to the method in the dynamic proxy base class; instantiate the dynamic proxy base class according to the custom annotation.
- the report delivery system customizes the annotation @HttpService in advance.
- When requesting to execute a specific method from the report management system first determine the specific method to be called, create a dynamic proxy base class ServiceProxyDTO for the method, and add a pre-created custom annotation to the method in the dynamic proxy base class @ HttpService, based on the spring framework to create httpclientbean, Spring's post-processor HttpServiceBeanProxyProcessor initializes it, and then scans all method fields in httpclientbean to determine whether the method adds the above custom annotation @HttpService.
- Step S40 The report management system obtains an instantiated dynamic proxy base class through the universal servlet interface, executes the method to be called according to the instantiated dynamic proxy base class, and sends an execution result to the report. Hair system.
- the report management system obtains the instantiated dynamic proxy base class ServiceProxyDTO passed in by the report delivery system through the servlet interface, and obtains the method name, parameter type, and parameter value to be called through the instantiated dynamic proxy base class ServiceProxyDTO; then based on The obtained data is called a specific method corresponding to the execution report management system through the reflection method.invoke method, and the specific method is implemented, and the specific execution result is returned to the report delivery system. It can be seen from the above scheme that the report management system only needs to set a general servlet interface. When a specific method at the report management system needs to be called, the parameters of the method are uploaded to the general servlet based on the dynamic proxy class. Interface to implement the specific method of calling the report management system. The report management system does not need to maintain the code of too many interfaces, and the report distribution system does not require frequent writing methods to use httpclient to call the interface, which improves the processing efficiency of the interface call.
- the report issuing system obtains the path information of the common servlet interface from the report management system; the report issuing system determines the method to be called, creates a dynamic proxy base class for the method, and instantiates the dynamic proxy base. Class; call the general servlet interface according to the path information, and send the instantiated dynamic proxy base class to the general servlet interface; the report management system obtains the instantiated dynamic proxy base class through the general servlet interface, and executes according to the instantiated dynamic proxy base class The method to be called sends the execution result to the report delivery system.
- the report management system does not need to implement multiple interface methods, but only needs to implement a common servlet interface.
- the report delivery system obtains the path information of the interface, accesses the interface according to the path information, and passes the dynamic proxy.
- the relevant parameters of the specific method to be called are uploaded to the interface, and the method execution result is obtained. It is not necessary to frequently write the HttpClient to call the specific implementation method of the remote interface, which not only simplifies the code, but also improves the processing efficiency of the interface call. .
- the present application also provides an interface calling device.
- FIG. 2 a schematic diagram of an internal structure of an interface calling device according to an embodiment of the present application is shown.
- the interface calling device 1 may be a PC (Personal Computer) or a terminal device such as a smart phone, a tablet computer, or a portable computer.
- the interface calling device 1 includes at least a memory 11, a processor 12, a network interface 13, and a communication bus.
- the memory 11 includes at least one type of readable storage medium, and the readable storage medium includes a flash memory, a hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, and the like.
- the memory 11 may be an internal storage unit of the interface calling device 1 in some embodiments, such as a hard disk of the interface calling device 1.
- the memory 11 may also be an external storage device of the interface calling device 1 in other embodiments, such as a plug-in hard disk, a smart memory card (SMC), and a secure digital (Secure Digital, SD) card, flash card, etc.
- the memory 11 may include both an internal storage unit of the interface calling device 1 and an external storage device.
- the memory 11 can be used not only to store application software and various types of data installed in the interface calling device 1, such as the code of the interface calling program 01, but also to temporarily store data that has been output or is to be output.
- the processor 12 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments, and is configured to run program codes or processes stored in the memory 11 Data, such as the execution interface call program 01.
- CPU central processing unit
- controller a controller
- microcontroller a microcontroller
- microprocessor or other data processing chip in some embodiments, and is configured to run program codes or processes stored in the memory 11 Data, such as the execution interface call program 01.
- the network interface 13 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface), and is generally used to establish a communication connection between the device 1 and other electronic devices.
- a standard wired interface such as a WI-FI interface
- the communication bus is used to implement connection communication between these components.
- the device 1 may further include a user interface.
- the user interface may include a display, an input unit such as a keyboard, and the optional user interface may further include a standard wired interface and a wireless interface.
- the display may be an LED display, a liquid crystal display, a touch-type liquid crystal display, an OLED (Organic Light-Emitting Diode, organic light emitting diode) touch device, or the like.
- the display may also be appropriately called a display screen or a display unit for displaying information processed in the interface calling device 1 and for displaying a visual user interface.
- FIG. 2 only shows the interface calling device 1 having the components 11-13 and the interface calling program 01.
- FIG. 1 does not constitute a limitation on the interface calling device 1 and may include There are fewer or more parts than shown, or some parts are combined, or different parts are arranged.
- the interface calling program 01 is stored in the memory 11; when the processor 12 executes the interface calling program 01 stored in the memory 11, the following steps are implemented:
- the report delivery system obtains path information of a general servlet interface from the report management system.
- the report delivery system determines a method to be called, creates a dynamic proxy base class for the method, and instantiates the dynamic proxy base class.
- the universal servlet interface is called according to the path information, and the instantiated dynamic proxy base class is sent to the universal servlet interface.
- the report management system obtains an instantiated dynamic proxy base class through the universal servlet interface, executes the method to be called according to the instantiated dynamic proxy base class, and sends an execution result to the report delivery system.
- the embodiment of the present application mainly includes a report management system and a report delivery system.
- a remote communication connection is established between the report management system and the report delivery system.
- the report management system is mainly used for report BI data source management, report management, and task management. , Log management and other functions.
- the report delivery system is mainly used for querying, downloading, and downloading task data at regular intervals.
- the report management system is a distributed system. When the report delivery system needs to call BI data sources, reports, and other data from the report management system, data is obtained through the external interface provided by the report management system.
- the report management system is configured with a common servlet interface and an interface configuration file; and the corresponding servlet request corresponding path information is configured through the interface configuration file.
- the path information is mainly used to find the dynamic proxy processing method commonly used by the report management system when the system of the remote report management system is invoked by the table issuing system.
- the report issuing system searches the corresponding general servlet interface according to the path information of the exposed interface.
- the report management system may actively send the interface configuration file to the report delivery system, and the report delivery system obtains path information from the file.
- the step of the report issuing system obtaining path information of the general servlet interface from the report management system includes: the report issuing system sends an interface information acquisition request to the report management system; the report The management system issues the interface configuration file to the report distribution system according to the interface information acquisition request; the report distribution system obtains the path of the general servlet interface of the report management system according to the interface configuration file information.
- the report delivery system accesses the configuration file of the general servlet interface of the report management system through httpclient to obtain the path information of the general servlet interface, and calls the servlet method of the report management system through the path information.
- the common servlet interface set by the report management system it can be understood as the proxy of the interface.
- the specific method of the remote server can be called on the report delivery system through the reflection mechanism.
- the remote server returns the result data of the execution of the specific method to the report delivery system.
- the report issuing system determines a method to be called, creates a dynamic proxy base class of the method, and instantiates the dynamic proxy base class.
- the steps include: the report issuing system determines a method to be called; and creating the method. Add a pre-created custom annotation to the method in the dynamic proxy base class; instantiate the dynamic proxy base class according to the custom annotation.
- the report delivery system customizes the annotation @HttpService in advance.
- When requesting to execute a specific method from the report management system first determine the specific method to be called, create a dynamic proxy base class ServiceProxyDTO for the method, and add a pre-created custom annotation to the method in the dynamic proxy base class @ HttpService, based on the spring framework to create httpclientbean, Spring's post-processor HttpServiceBeanProxyProcessor initializes it, and then scans all method fields in httpclientbean to determine whether the method adds the above custom annotation @HttpService.
- the report management system obtains the instantiated dynamic proxy base class ServiceProxyDTO passed into the report delivery system through the servlet interface, and obtains the method name, parameter type, and parameter value to be called through the instantiated dynamic proxy base class ServiceProxyDTO;
- the obtained data is called a specific method corresponding to the execution report management system through the reflection method.invoke method, and the specific method is implemented, and the specific execution result is returned to the report delivery system.
- the report management system only needs to set a general servlet interface.
- the parameters of the method are uploaded to the general servlet based on the dynamic proxy class.
- the report management system does not need to maintain the code of too many interfaces, and the report distribution system does not require frequent writing methods to use httpclient to call the interface, which improves the processing efficiency of the interface call.
- the report issuing system obtains the path information of the general servlet interface from the report management system; the report issuing system determines the method to be called, creates a dynamic proxy base class of the method, and instantiates the dynamic proxy base. Class; call the general servlet interface according to the path information, and send the instantiated dynamic proxy base class to the general servlet interface; the report management system obtains the instantiated dynamic proxy base class through the general servlet interface, and executes according to the instantiated dynamic proxy base class The method to be called sends the execution result to the report delivery system.
- the report management system does not need to implement multiple interface methods, but only needs to implement a common servlet interface.
- the report delivery system obtains the path information of the interface, accesses the interface according to the path information, and passes the dynamic proxy.
- the relevant parameters of the specific method to be called are uploaded to the interface, and the method execution result is obtained. It is not necessary to frequently write the HttpClient to call the specific implementation method of the remote interface, which not only simplifies the code, but also improves the processing efficiency of the interface call. .
- the interface calling program may also be divided into one or more modules, and the one or more modules are stored in the memory 11 and processed by one or more processors (in this embodiment, The processor 12) executes to complete the present application.
- the modules referred to in the present application refer to a series of computer program instruction segments capable of performing specific functions, and are used to describe the execution process of the interface calling program in the interface calling device.
- FIG. 3 a schematic diagram of a program module of an interface calling program in an embodiment of the interface calling device of the present application.
- the interface calling program can be divided into an information acquisition module 10, a dynamic proxy module 20, and a request.
- the sending module 30 and the data receiving module 40 exemplarily:
- the information obtaining module 10 is configured to obtain path information of a general servlet interface from the report management system;
- the dynamic proxy module 20 is configured to determine a method to be called, create a dynamic proxy base class for the method, and instantiate the dynamic proxy base class;
- the request sending module 30 is configured to call the universal servlet interface according to the path information, and send the instantiated dynamic proxy base class to the universal servlet interface for the report management system to obtain through the universal servlet interface.
- the data receiving module 40 is configured to receive an execution result sent by the report management system.
- an embodiment of the present application further provides a computer-readable storage medium.
- the computer-readable storage medium stores an interface calling program, and the interface calling program can be executed by one or more processors to implement the following operations:
- the report issuing system obtains path information of a general servlet interface from the report management system;
- the report issuing system determines a method to be called, creates a dynamic proxy base class of the method, and instantiates the dynamic proxy base class;
- the report management system obtains an instantiated dynamic proxy base class through the universal servlet interface, executes the method to be called according to the instantiated dynamic proxy base class, and sends an execution result to the report delivery system.
- the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, also by hardware, but in many cases the former is better.
- Implementation Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product.
- the computer software product is stored in a storage medium (such as ROM / RAM) as described above. , Magnetic disk, optical disc), including a number of instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the embodiments of the present application.
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
一种接口调用方法,装置以及计算机可读存储介质,该方法包括:报表下发***从报表管理***获取通用Servlet接口的路径信息(S10);报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化动态代理基类(S20);根据路径信息调用通用Servlet接口,将实例化后的动态代理基类发送至通用Servlet接口(S30);报表管理***通过通用Servlet接口获取实例化的动态代理基类,根据实例化的动态代理基类执行待调用的方法,将执行结果发送至报表下发***(S40)。该方法解决了报表管理***处代码冗余,且对于报表下发***的接口调用的处理效率低下的技术问题。
Description
本申请基于巴黎公约申明享有2018年07月18日递交的申请号为201810791995.6、名称为“接口调用方法、装置及计算机可读存储介质”的中国专利申请的优先权,该中国专利申请的整体内容以参考的方式结合在本申请中。
本申请涉及计算机技术领域,尤其涉及一种接口调用方法、装置及计算机可读存储介质。
报表管理***用于报表BI(Business Intelligence,商业智能)数据源管理、报表管理、任务管理、日志管理等功能;报表下发***用于报表数据的查询、下载、定时采集任务数据的下发。报表管理***为分布式***,当报表下发***需要从报表管理***调用BI源、报表等数据时,通过报表管理***提供给外部的接口实现数据的获取。
常规的做法是:报表管理***通过servlet提供接口给外部调用;报表下发***通过httpclient调用报表管理***提供的接口返回需要的数据。这种方法的缺点在于:当报表下发***频繁调用报表管理***的多个接口时,报表管理***需要提供多个接口,报表下发***需要频繁的写方法利用httpclient去调用接口,导致报表管理***处代码冗余,且对于报表下发***的接口调用的处理效率低下。
发明内容
本申请提供一种接口调用方法、装置及计算机可读存储介质,其主要目的在于解决报表管理***处代码冗余,且对于报表下发***的接口调用的处理效率低下的技术问题。
为实现上述目的,本申请还提供一种接口调用方法,该方法包括:
所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息;
所述报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;
根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口;
所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***。
此外,为实现上述目的,本申请还提供一种接口调用装置,该装置包括存储器和处理器,所述存储器中存储有可在所述处理器上运行的接口调用程序,所述接口调用程序被所述处理器执行时实现如下步骤:
从所述报表管理***获取通用Servlet接口的路径信息;
确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;
根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口,以供所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,并根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述接口调用装置;
接收所述报表管理***发送的执行结果。
此外,为实现上述目的,本申请还提供一种计算机可读存储介质,所述计算机可读存储介质上存储有接口调用程序,所述接口调用程序可被一个或者多个处理器执行,以实现如下步骤:
从所述报表管理***获取通用Servlet接口的路径信息;
确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;
根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口,以供所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,并根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述接口调用装置;
接收所述报表管理***发送的执行结果。
本申请提出的接口调用方法、装置及计算机可读存储介质,报表下发系 统从报表管理***获取通用Servlet接口的路径信息;报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化动态代理基类;根据路径信息调用通用Servlet接口,将实例化后的动态代理基类发送至通用Servlet接口;报表管理***通过通用Servlet接口获取实例化的动态代理基类,根据实例化的动态代理基类执行待调用的方法,将执行结果发送至报表下发***。本申请的方案中,报表管理***不需要实现多个接口方法,只需要实现一个通用Servlet接口即可,报表下发***获取到该接口的路径信息,根据路径信息访问该接口,并通过动态代理的方式将要调用的具体的方法的相关参数上传到该接口,进而实现方法执行结果的获取,不需要频繁的写HttpClient调用远程接口具体实现方法,不仅简化了代码,而且提高了接口调用的处理效率。
图1为本申请一实施例提供的接口调用方法的流程示意图;
图2为本申请一实施例提供的接口调用装置的内部结构示意图;
图3为本申请一实施例提供的接口调用装置中接口调用程序的模块示意图。
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请提供一种接口调用方法。参照图1所示,为本申请一实施例提供的接口调用方法的流程示意图。该方法可以由一个装置执行,该装置可以由软件和/或硬件实现。
在本实施例中,接口调用方法包括:
步骤S10,所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息。
本申请实施例中主要包括报表管理***和报表下发***,报表管理*** 和报表下发***之间建立远程通讯连接,其中,报表管理***主要用于报表BI数据源管理、报表管理、任务管理、日志管理等功能。报表下发***主要用于报表数据的查询、下载、定时采集任务数据的下发。报表管理***为分布式***,当报表下发***需要从报表管理***调用BI数据源、报表等数据时,通过报表管理***提供给外部的接口实现数据的获取。
报表管理***配置好通用Servlet接口以及接口配置文件;通过接口配置文件配置相应的servlet请求对应的路径信息该路径信息主用于表下发***调用远程报表管理***的接口方法时能找到报表管理***通用的动态代理处理方法,报表下发***根据暴露的接口的路径信息查找对应的上述通用Servlet接口。其中,报表管理***可以主动将该接口配置文件下发到报表下发***,报表下发***从该文件中获取路径信息。或者,在其他实施例中,报表下发***从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:所述报表下发***向所述报表管理***发送接口信息获取请求;所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;所述报表下发***根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。具体地,报表下发***通过httpclient访问报表管理***的通用Servlet接口的配置文件,以获取该通用Servlet接口的路径信息,通过路径信息调用报表管理***的servlet方法。
关于报表管理***设置的通用Servlet接口,此处可以理解为接口的代理,在确定方法名、参数类型以及参数值后,就可以通过反射机制在报表下发***调用远程服务器端的具体方法,并由远程服务器端返回执行具体方法的结果数据给报表下发***。
步骤S20,所述报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类。
步骤S30,根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口。
具体地,报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类的步骤包括:所述报表下发***确定待调用的方法;创建该方法的动态代理基类,并在所述动态代理基类中为所述方法添加预先创建的自定义注解;根据所述自定义注解将所述动态代理基类实例化。
报表下发***预先自定义注解@HttpService。在需要向报表管理***请求执行具体的方法时,先确定待调用的具体方法,创建该方法的动态代理基类ServiceProxyDTO,并在动态代理基类中为所述方法添加预先创建的自定义注解@HttpService,基于spring框架创建httpclientbean,Spring的后置处理器HttpServiceBeanProxyProcessor将其初始化,然后对httpclientbean中的所有方法字段进行扫描,判断方法是否添加了上述自定义注解@HttpService,当通过扫描找到添加了自定义注解@HttpService的方法后,实例化该方法的动态基类ServiceProxyDTO的实例名,方法名,参数值,参数类型等具体实例参数值。将实例化后的动态代理基类ServiceProxyDTO作为参数,通过Httpclient传到报表管理***的通用servlet接口里面去。
步骤S40,所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***。
报表管理***通过servlet接口获取到报表下发***传入的实例化后的动态代理基类ServiceProxyDTO,通过实例化后的动态代理基类ServiceProxyDTO获取需要调用的方法名,参数类型以及参数值;然后基于获取的上述数据,通过反射method.invoke方法调用执行报表管理***对应的具体方法,并实现该具体方法,将执行的具体结果返回到报表下发***。从上述方案中可以看出报表管理***处只需要设置一个通用的Servlet接口即可,在需要调用报表管理***处的具体的方法时,基于动态代理类将该方法的参数上传到上述通用的Servlet接口,以实现调用报表管理***的具体方法。报表管理***无需维护过多接口的代码,报表下发***不需要频繁的写方法利用httpclient去调用接口,提高了接口调用的处理效率。
本实施例提出的接口调用方法,报表下发***从报表管理***获取通用Servlet接口的路径信息;报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化动态代理基类;根据路径信息调用通用Servlet接口,将实例化后的动态代理基类发送至通用Servlet接口;报表管理***通过通用Servlet接口获取实例化的动态代理基类,根据实例化的动态代理基类执行待调用的方法,将执行结果发送至报表下发***。本申请的方案中,报表管理***不需要实现多个接口方法,只需要实现一个通用Servlet接口即可,报表 下发***获取到该接口的路径信息,根据路径信息访问该接口,并通过动态代理的方式将要调用的具体的方法的相关参数上传到该接口,进而实现方法执行结果的获取,不需要频繁的写HttpClient调用远程接口具体实现方法,不仅简化了代码,而且提高了接口调用的处理效率。
本申请还提供一种接口调用装置。参照图2所示,为本申请一实施例提供的接口调用装置的内部结构示意图。
在本实施例中,接口调用装置1可以是PC(Personal Computer,个人电脑),也可以是智能手机、平板电脑、便携计算机等终端设备。该接口调用装置1至少包括存储器11、处理器12,网络接口13以及通信总线。
其中,存储器11至少包括一种类型的可读存储介质,所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如,SD或DX存储器等)、磁性存储器、磁盘、光盘等。存储器11在一些实施例中可以是接口调用装置1的内部存储单元,例如该接口调用装置1的硬盘。存储器11在另一些实施例中也可以是接口调用装置1的外部存储设备,例如接口调用装置1上配备的插接式硬盘,智能存储卡(Smart Media Card,SMC),安全数字(Secure Digital,SD)卡,闪存卡(Flash Card)等。进一步地,存储器11还可以既包括接口调用装置1的内部存储单元也包括外部存储设备。存储器11不仅可以用于存储安装于接口调用装置1的应用软件及各类数据,例如接口调用程序01的代码等,还可以用于暂时地存储已经输出或者将要输出的数据。
处理器12在一些实施例中可以是一中央处理器(Central Processing Unit,CPU)、控制器、微控制器、微处理器或其他数据处理芯片,用于运行存储器11中存储的程序代码或处理数据,例如执行接口调用程序01等。
网络接口13可选的可以包括标准的有线接口、无线接口(如WI-FI接口),通常用于在该装置1与其他电子设备之间建立通信连接。
通信总线用于实现这些组件之间的连接通信。
可选地,该装置1还可以包括用户接口,用户接口可以包括显示器(Display)、输入单元比如键盘(Keyboard),可选的用户接口还可以包括标准的有线接口、无线接口。可选地,在一些实施例中,显示器可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode,有机发光二极管)触摸器等。其中,显示器也可以适当的称为显示屏 或显示单元,用于显示在接口调用装置1中处理的信息以及用于显示可视化的用户界面。
图2仅示出了具有组件11-13以及接口调用程序01的接口调用装置1,本领域技术人员可以理解的是,图1示出的结构并不构成对接口调用装置1的限定,可以包括比图示更少或者更多的部件,或者组合某些部件,或者不同的部件布置。
在图2所示的装置1实施例中,存储器11中存储有接口调用程序01;处理器12执行存储器11中存储的接口调用程序01时实现如下步骤:
所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息。
所述报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类。
根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口。
所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***。
本申请实施例中主要包括报表管理***和报表下发***,报表管理***和报表下发***之间建立远程通讯连接,其中,报表管理***主要用于报表BI数据源管理、报表管理、任务管理、日志管理等功能。报表下发***主要用于报表数据的查询、下载、定时采集任务数据的下发。报表管理***为分布式***,当报表下发***需要从报表管理***调用BI数据源、报表等数据时,通过报表管理***提供给外部的接口实现数据的获取。
报表管理***配置好通用Servlet接口以及接口配置文件;通过接口配置文件配置相应的servlet请求对应的路径信息。该路径信息主用于表下发***调用远程报表管理***的接口方法时能找到报表管理***通用的动态代理处理方法,报表下发***根据暴露的接口的路径信息查找对应的上述通用Servlet接口。其中,报表管理***可以主动将该接口配置文件下发到报表下发***,报表下发***从该文件中获取路径信息。或者,在其他实施例中,报表下发***从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:所述报表下发***向所述报表管理***发送接口信息获取请求;所述报 表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;所述报表下发***根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。具体地,报表下发***通过httpclient访问报表管理***的通用Servlet接口的配置文件,以获取该通用Servlet接口的路径信息,通过路径信息调用报表管理***的servlet方法。
关于报表管理***设置的通用Servlet接口,此处可以理解为接口的代理,在确定方法名、参数类型以及参数值后,就可以通过反射机制在报表下发***调用远程服务器端的具体方法,并由远程服务器端返回执行具体方法的结果数据给报表下发***。
具体地,报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类的步骤包括:所述报表下发***确定待调用的方法;创建该方法的动态代理基类,并在所述动态代理基类中为所述方法添加预先创建的自定义注解;根据所述自定义注解将所述动态代理基类实例化。
报表下发***预先自定义注解@HttpService。在需要向报表管理***请求执行具体的方法时,先确定待调用的具体方法,创建该方法的动态代理基类ServiceProxyDTO,并在动态代理基类中为所述方法添加预先创建的自定义注解@HttpService,基于spring框架创建httpclientbean,Spring的后置处理器HttpServiceBeanProxyProcessor将其初始化,然后对httpclientbean中的所有方法字段进行扫描,判断方法是否添加了上述自定义注解@HttpService,当通过扫描找到添加了自定义注解@HttpService的方法后,实例化该方法的动态基类ServiceProxyDTO的实例名,方法名,参数值,参数类型等具体实例参数值。将实例化后的动态代理基类ServiceProxyDTO作为参数,通过Httpclient传到报表管理***的通用servlet接口里面去。
报表管理***通过servlet接口获取到报表下发***传入的实例化后的动态代理基类ServiceProxyDTO,通过实例化后的动态代理基类ServiceProxyDTO获取需要调用的方法名,参数类型以及参数值;然后基于获取的上述数据,通过反射method.invoke方法调用执行报表管理***对应的具体方法,并实现该具体方法,将执行的具体结果返回到报表下发***。
从上述方案中可以看出报表管理***处只需要设置一个通用的Servlet接口即可,在需要调用报表管理***处的具体的方法时,基于动态代理类将该 方法的参数上传到上述通用的Servlet接口,以实现调用报表管理***的具体方法。报表管理***无需维护过多接口的代码,报表下发***不需要频繁的写方法利用httpclient去调用接口,提高了接口调用的处理效率。
本实施例提出的接口调用装置,报表下发***从报表管理***获取通用Servlet接口的路径信息;报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化动态代理基类;根据路径信息调用通用Servlet接口,将实例化后的动态代理基类发送至通用Servlet接口;报表管理***通过通用Servlet接口获取实例化的动态代理基类,根据实例化的动态代理基类执行待调用的方法,将执行结果发送至报表下发***。本申请的方案中,报表管理***不需要实现多个接口方法,只需要实现一个通用Servlet接口即可,报表下发***获取到该接口的路径信息,根据路径信息访问该接口,并通过动态代理的方式将要调用的具体的方法的相关参数上传到该接口,进而实现方法执行结果的获取,不需要频繁的写HttpClient调用远程接口具体实现方法,不仅简化了代码,而且提高了接口调用的处理效率。
可选地,在其他的实施例中,接口调用程序还可以被分割为一个或者多个模块,一个或者多个模块被存储于存储器11中,并由一个或多个处理器(本实施例为处理器12)所执行以完成本申请,本申请所称的模块是指能够完成特定功能的一系列计算机程序指令段,用于描述接口调用程序在接口调用装置中的执行过程。
例如,参照图3所示,为本申请接口调用装置一实施例中的接口调用程序的程序模块示意图,该实施例中,接口调用程序可以被分割为信息获取模块10、动态代理模块20、请求发送模块30和数据接收模块40,示例性地:
信息获取模块10用于:从所述报表管理***获取通用Servlet接口的路径信息;
动态代理模块20用于:确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;
请求发送模块30用于:根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口,以供所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,并根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述接口调用装 置;
数据接收模块40用于:接收所述报表管理***发送的执行结果。
上述信息获取模块10、动态代理模块20、请求发送模块30和数据接收模块40等程序模块被执行时所实现的功能或操作步骤与上述实施例大体相同,在此不再赘述。
此外,本申请实施例还提出一种计算机可读存储介质,所述计算机可读存储介质上存储有接口调用程序,所述接口调用程序可被一个或多个处理器执行,以实现如下操作:
所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息;
所述报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;
根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口;
所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***。
本申请计算机可读存储介质具体实施方式与上述接口调用装置和方法各实施例基本相同,在此不作累述。
需要说明的是,上述本申请实施例序号仅仅为了描述,不代表实施例的优劣。并且本文中的术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、装置、物品或者方法不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、装置、物品或者方法所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、装置、物品或者方法中还存在另外的相同要素。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在如上所述的一个存储介质(如ROM/RAM、 磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本申请的专利保护范围内。
Claims (20)
- 一种接口调用方法,其特征在于,所述方法包括:所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息;所述报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口;所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***。
- 如权利要求1所述的接口调用方法,其特征在于,所述报表下发***确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类的步骤包括:所述报表下发***确定待调用的方法;创建该方法的动态代理基类,并在所述动态代理基类中为该方法添加预先创建的自定义注解;根据所述自定义注解将所述动态代理基类实例化。
- 如权利要求2所述的接口调用方法,其特征在于,所述根据所述自定义注解将所述动态代理基类实例化的步骤包括:所述报表下发***初始化httpclientbean,对所述httpclientbean中所有方法字段进行扫描,以确定添加了所述自定义注解的方法;为添加了所述自定义注解的方法的动态代理基类设置实例参数,以将所述动态代理基类实例化,所述实例参数包括方法名、参数值和参数类型。
- 如权利要求2所述的接口调用方法,其特征在于,所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***的步骤包括:所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,获取所述待调用的方法的参数,其中,所述方法的参数包括方法名、参数值和参数类型;根据获取的方法的参数执行对应的方法,将执行结果发送至所述报表下发***。
- 如权利要求2所述的接口调用方法,其特征在于,所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:所述报表下发***向所述报表管理***发送接口信息获取请求;所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;所述报表下发***根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。
- 如权利要求3所述的接口调用方法,其特征在于,所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:所述报表下发***向所述报表管理***发送接口信息获取请求;所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;所述报表下发***根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。
- 如权利要求4所述的接口调用方法,其特征在于,所述报表下发***从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:所述报表下发***向所述报表管理***发送接口信息获取请求;所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;所述报表下发***根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。
- 一种接口调用装置,其特征在于,所述装置包括存储器和处理器,所述存储器上存储有可在所述处理器上运行的接口调用程序,所述接口调用程序被所述处理器执行时实现如下步骤:从所述报表管理***获取通用Servlet接口的路径信息;确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基 类发送至所述通用Servlet接口,以供所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,并根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述接口调用装置;接收所述报表管理***发送的执行结果。
- 如权利要求8所述的接口调用装置,其特征在于,所述确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类的步骤包括:确定待调用的方法;创建该方法的动态代理基类,并在所述动态代理基类中为该方法添加预先创建的自定义注解;根据所述自定义注解将所述动态代理基类实例化。
- 如权利要求9所述的接口调用装置,其特征在于,所述根据所述自定义注解将所述动态代理基类实例化的步骤包括:初始化httpclientbean,对所述httpclientbean中所有方法字段进行扫描,以确定添加了所述自定义注解的方法;为添加了所述自定义注解的方法的动态代理基类设置实例参数,以将所述动态代理基类实例化,所述实例参数包括方法名、参数值和参数类型。
- 如权利要求9所述的接口调用装置,其特征在于,所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***的步骤包括:所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,获取所述待调用的方法的参数,其中,所述方法的参数包括方法名、参数值和参数类型;根据获取的方法的参数执行对应的方法,将执行结果发送至所述报表下发***。
- 如权利要求9所述的接口调用装置,其特征在于,所述从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:向所述报表管理***发送接口信息获取请求,其中,所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径 信息。
- 如权利要求10所述的接口调用装置,其特征在于,所述从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:向所述报表管理***发送接口信息获取请求,其中,所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。
- 如权利要求11所述的接口调用装置,其特征在于,所述从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:向所述报表管理***发送接口信息获取请求,其中,所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有接口调用程序,所述接口调用程序可被一个或者多个处理器执行,以实现如下步骤:从所述报表管理***获取通用Servlet接口的路径信息;确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类;根据所述路径信息调用所述通用Servlet接口,将实例化后的动态代理基类发送至所述通用Servlet接口,以供所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,并根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述接口调用装置;接收所述报表管理***发送的执行结果。
- 如权利要求15所述的计算机可读存储介质,其特征在于,所述确定待调用的方法,创建该方法的动态代理基类,并实例化所述动态代理基类的步骤包括:确定待调用的方法;创建该方法的动态代理基类,并在所述动态代理基类中为所述方法添加预先创建的自定义注解;根据所述自定义注解将所述动态代理基类实例化。
- 如权利要求16所述的计算机可读存储介质,其特征在于,所述根据所述自定义注解将所述动态代理基类实例化的步骤包括:初始化httpclientbean,对所述httpclientbean中所有方法字段进行扫描,以确定添加了所述自定义注解的方法;为添加了所述自定义注解的方法的动态代理基类设置实例参数,以将所述动态代理基类实例化,所述实例参数包括方法名、参数值和参数类型。
- 如权利要求15所述的计算机可读存储介质,其特征在于,所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,根据所述实例化的动态代理基类执行所述待调用的方法,将执行结果发送至所述报表下发***的步骤包括:所述报表管理***通过所述通用Servlet接口获取实例化的动态代理基类,获取所述待调用的方法的参数,其中,所述方法的参数包括方法名、参数值和参数类型;根据获取的方法的参数执行对应的方法,将执行结果发送至所述报表下发***。
- 如权利要求16所述的计算机可读存储介质,其特征在于,所述从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:向所述报表管理***发送接口信息获取请求,其中,所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。
- 如权利要求17所述的计算机可读存储介质,其特征在于,所述从所述报表管理***获取通用Servlet接口的路径信息的步骤包括:向所述报表管理***发送接口信息获取请求,其中,所述报表管理***根据所述接口信息获取请求,将所述接口配置文件下发至所述报表下发***;根据所述接口配置文件获取所述报表管理***的通用Servlet接口的路径信息。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810791995.6A CN109254808A (zh) | 2018-07-18 | 2018-07-18 | 接口调用方法、装置及计算机可读存储介质 |
CN201810791995.6 | 2018-07-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020015170A1 true WO2020015170A1 (zh) | 2020-01-23 |
Family
ID=65048682
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/107724 WO2020015170A1 (zh) | 2018-07-18 | 2018-09-26 | 接口调用方法、装置及计算机可读存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN109254808A (zh) |
WO (1) | WO2020015170A1 (zh) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110069248A (zh) * | 2019-03-16 | 2019-07-30 | 平安城市建设科技(深圳)有限公司 | 接口数据的调用方法、装置、设备及计算机可读存储介质 |
CN111191246A (zh) * | 2019-12-19 | 2020-05-22 | 杭州安恒信息技术股份有限公司 | 一种基于Spring注解的安全开发校验方法 |
CN111209122B (zh) * | 2019-12-24 | 2024-06-11 | 广州华多网络科技有限公司 | 接口调用方法、装置、电子设备及存储介质 |
CN112199092B (zh) * | 2020-09-17 | 2024-03-15 | 上海硬通网络科技有限公司 | 应用的开发方法、装置及电子设备 |
CN113608779B (zh) * | 2021-08-10 | 2023-12-26 | 平安国际智慧城市科技股份有限公司 | 服务接口配置方法、装置、设备及存储介质 |
CN114020485A (zh) * | 2021-09-30 | 2022-02-08 | 中国人民财产保险股份有限公司 | 日志记录的方法及装置 |
CN114489830B (zh) * | 2021-12-23 | 2024-06-07 | 阿里巴巴(中国)有限公司 | 配置页面操作方法、处理方法和计算设备 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103152433A (zh) * | 2013-01-14 | 2013-06-12 | 广东电子工业研究院有限公司 | 一种分布式服务端框架及其使用、交互、请求处理方法 |
CN103425462A (zh) * | 2012-05-14 | 2013-12-04 | 阿里巴巴集团控股有限公司 | 一种工作流数据持久化的方法和装置 |
CN106354481A (zh) * | 2015-07-13 | 2017-01-25 | 阿里巴巴集团控股有限公司 | 对http请求进行统一映射的方法和设备 |
CN107678864A (zh) * | 2017-01-13 | 2018-02-09 | 北京资配易投资顾问有限公司 | 接口的调用方法及*** |
CN107770225A (zh) * | 2016-08-22 | 2018-03-06 | 北京京东尚科信息技术有限公司 | 一种 webService访问***和访问webService的方法 |
CN108234670A (zh) * | 2018-01-31 | 2018-06-29 | 北京中安智达科技有限公司 | 一种基于zookeeper和netty的分布式远程调用方法 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7519977B2 (en) * | 2004-06-22 | 2009-04-14 | International Business Machines Corporation | System and method for asynchronously invoking dynamic proxy interface using supplemental interfaces |
CN101266542B (zh) * | 2008-02-01 | 2011-06-29 | 中国建设银行股份有限公司 | 一种在容器中装载组件的方法及装置 |
-
2018
- 2018-07-18 CN CN201810791995.6A patent/CN109254808A/zh active Pending
- 2018-09-26 WO PCT/CN2018/107724 patent/WO2020015170A1/zh active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103425462A (zh) * | 2012-05-14 | 2013-12-04 | 阿里巴巴集团控股有限公司 | 一种工作流数据持久化的方法和装置 |
CN103152433A (zh) * | 2013-01-14 | 2013-06-12 | 广东电子工业研究院有限公司 | 一种分布式服务端框架及其使用、交互、请求处理方法 |
CN106354481A (zh) * | 2015-07-13 | 2017-01-25 | 阿里巴巴集团控股有限公司 | 对http请求进行统一映射的方法和设备 |
CN107770225A (zh) * | 2016-08-22 | 2018-03-06 | 北京京东尚科信息技术有限公司 | 一种 webService访问***和访问webService的方法 |
CN107678864A (zh) * | 2017-01-13 | 2018-02-09 | 北京资配易投资顾问有限公司 | 接口的调用方法及*** |
CN108234670A (zh) * | 2018-01-31 | 2018-06-29 | 北京中安智达科技有限公司 | 一种基于zookeeper和netty的分布式远程调用方法 |
Also Published As
Publication number | Publication date |
---|---|
CN109254808A (zh) | 2019-01-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020015170A1 (zh) | 接口调用方法、装置及计算机可读存储介质 | |
WO2020015166A1 (zh) | 图表组件的创建方法、装置及计算机可读存储介质 | |
CN109997126B (zh) | 事件驱动提取、变换、加载(etl)处理 | |
CN108874924B (zh) | 搜索服务的创建方法、装置及计算机可读存储介质 | |
CN107656729B (zh) | 列表视图的更新装置、方法及计算机可读存储介质 | |
WO2021184725A1 (zh) | 用户界面测试方法、装置、存储介质及计算机设备 | |
WO2019227715A1 (zh) | 数据处理方法、装置及计算机可读存储介质 | |
JP2018528559A (ja) | ソフトウエア開発キットによってデータ追跡を実現する方法及びシステム | |
WO2021098392A1 (zh) | 应用部署方法、装置、电子设备及存储介质 | |
CN110737659A (zh) | 图数据存储和查询方法、装置及计算机可读存储介质 | |
US9037614B1 (en) | Secondary mappings to enable code changes without schema updates | |
US20130117652A1 (en) | Techniques to generate custom electronic forms | |
US11580294B2 (en) | Techniques for web framework detection | |
CN111177113B (zh) | 数据迁移方法、装置、计算机设备和存储介质 | |
CN1794230A (zh) | 以透明方式公开计算机生成文档中嵌套数据的方法和*** | |
CN110941779A (zh) | 加载页面的方法、装置、存储介质及电子设备 | |
WO2019071898A1 (zh) | 电子装置、数据库查询脚本生成方法及存储介质 | |
CN111274263A (zh) | 可视化数据库变更语句生成方法、装置及存储介质 | |
CN114556317A (zh) | 通过版本散列链接图形的文档跟踪 | |
US20140136578A1 (en) | Techniques to manage virtual files | |
CN111723077A (zh) | 数据字典维护方法、装置及计算机设备 | |
US20140172960A1 (en) | Electronic device and method for managing tags of virtual machines | |
WO2019136813A1 (zh) | Api文件管理方法、服务器及存储介质 | |
WO2019062020A1 (zh) | 异步任务统一处理方法、装置及存储介质 | |
US10789048B2 (en) | Namespace and class utilities for managed packages |
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: 18927106 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: 18927106 Country of ref document: EP Kind code of ref document: A1 |