WO2020192134A1 - Procédé et appareil de gestion d'exceptions basés sur spring mvc, et dispositif informatique et support de stockage - Google Patents

Procédé et appareil de gestion d'exceptions basés sur spring mvc, et dispositif informatique et support de stockage Download PDF

Info

Publication number
WO2020192134A1
WO2020192134A1 PCT/CN2019/117506 CN2019117506W WO2020192134A1 WO 2020192134 A1 WO2020192134 A1 WO 2020192134A1 CN 2019117506 W CN2019117506 W CN 2019117506W WO 2020192134 A1 WO2020192134 A1 WO 2020192134A1
Authority
WO
WIPO (PCT)
Prior art keywords
processor
resource request
view object
abnormal
exception
Prior art date
Application number
PCT/CN2019/117506
Other languages
English (en)
Chinese (zh)
Inventor
许永夫
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020192134A1 publication Critical patent/WO2020192134A1/fr

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
    • G06F9/449—Object-oriented method invocation or resolution

Definitions

  • This application relates to a Spring MVC-based exception handling method, device, computer equipment and storage medium.
  • the Spring MVC framework is designed around a DispatcherServlet interface class.
  • This interface class implements the basic functions of the front controller, distributes received data requests to each handler object (Handler), and supports configurable processor mapping, View rendering, localization.
  • the DispatcherServlet interface class is implemented through various configuration files. By defining various implementation classes in these configuration files, the basic functions of the front controller can be realized.
  • a Spring MVC-based exception handling method, device, computer equipment, and storage medium are provided.
  • An exception handling method based on Spring MVC includes:
  • the front-end controller generates an abnormal page view object according to the new model view object; the abnormal page view object is used to enable the client to display a page including abnormal information corresponding to the abnormal type code.
  • a Spring MVC-based exception handling device includes:
  • the resource request acquisition module is used to acquire the resource request sent by the client through the front controller;
  • the target processor object acquisition module is configured to determine the corresponding target processor object according to the resource identifier in the resource request, and process the resource request through the target processor object to obtain a model view object;
  • the callback processing module is used to call the callback function of the interceptor interface class to verify the model view object
  • the exception handling module is used to call the exception handling object to process the exception type code to obtain a new model view object when the callback function returns the exception type code; generate a new model view object by the front controller according to the new model view object An abnormal page view object; the abnormal page view object is used to make the client display a page that includes abnormal information corresponding to the abnormal type code.
  • 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 front-end controller generates an abnormal page view object according to the new model view object; the abnormal page view object is used to enable the client to display a page including abnormal information corresponding to the abnormal type code.
  • One or more non-volatile computer-readable storage media storing computer-readable instructions.
  • the one or more processors execute the following steps:
  • the front-end controller generates an abnormal page view object according to the new model view object; the abnormal page view object is used to enable the client to display a page including abnormal information corresponding to the abnormal type code.
  • Fig. 1 is an application scenario diagram of an exception handling method based on Spring MVC according to one or more embodiments.
  • Fig. 2 is a schematic flowchart of an exception handling method based on Spring MVC according to one or more embodiments.
  • Fig. 3 is a schematic diagram of a framework of an exception handling method based on Spring MVC according to one or more embodiments.
  • Fig. 4 is a block diagram of an exception handling device based on Spring MVC according to one or more embodiments.
  • Figure 5 is a block diagram of a computer device according to one or more embodiments.
  • the Spring MVC-based exception handling method provided in this application can be applied to the application environment shown in Figure 1.
  • the terminal 102 and the web server 104 communicate through the network.
  • the terminal 102 obtains the resource request triggered by the user in the browser, and sends the resource request to the web server 104 through the network.
  • the web server 104 obtains the resource request sent by the client through the front-end controller, and according to the resource identifier in the resource request
  • the symbol determines the corresponding target processor object, and processes the resource request through the obtained target processor object to obtain the model view object; then calls the callback function of the interceptor interface class to verify the model view object; when the callback function returns the exception type code ,
  • the front controller can call the exception handling object to process the exception type code to obtain a new model view object; the front controller generates an exception page view object according to the new model view object; when the client receives the exception page view object, it can render Display the page that includes the exception information corresponding to the exception type code.
  • the terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
  • the web server 104 may be implemented by an independent server or a server cluster composed of multiple servers.
  • a Spring MVC exception handling method is provided. Taking the method applied to the web server 104 in FIG. 1 as an example for description, the method includes the following steps:
  • Step S202 Obtain the resource request sent by the client through the front-end controller.
  • the resource request is an HTTP message generated by the client according to the currently acquired resource identifier (URL).
  • the resource identifier is used to uniquely identify the resource to be requested.
  • the client When a user visits a website, the client generates a resource request according to the URL corresponding to the visited website, and sends the resource request to the web server through the network.
  • the web server After the web server receives the resource request, it checks the resource identifier in the resource request. If it is found to be a static resource request, it forwards the request to the default server program (Default-servlet-handler) of the web server Through processing, the target data corresponding to the resource request is obtained, and the target resource carrier object corresponding to the resource request is generated according to the target data and returned to the client.
  • Default-servlet-handler the default server program
  • the server program If it is not a request for a static resource, match the server program corresponding to the resource identifier according to the configuration file, and forward the resource request to the front controller of the server program. After the front controller receives the resource request, it calls the The other components included in the server program process the resource request.
  • the client requests a static resource (*.htm, a file with a suffix of *.htm), it will forward the request directly to the web server, and then the web server will retrieve the content from the file system and send it back to the client browser Perform analysis and execution.
  • a static resource *.htm, a file with a suffix of *.htm
  • the web server will retrieve the content from the file system and send it back to the client browser Perform analysis and execution.
  • dynamic resources (*.jsp, *.asp, *.aspx, *.php)
  • the front controller is a pre-defined implementation class inherited from the SpringDispatcherServlet interface class in the Spring MVC framework.
  • the front controller can be, for example, WebSupportDispatcherServlet. It is the center of the entire process control and controls the scheduling and execution of other interface classes.
  • the data corresponding to the URL in the resource request is processed by the processor defined by the business processing layer and then encapsulated into a model (Model) in the MVC architecture, and then the model (Model) is returned to the corresponding interface (View) for display.
  • the implementation class is the specific implementation method of the interface class. For example, an interface class has three implementation classes A, B, and C, which are different types of implementation classes. By determining that the object referenced by the interface class is the implementation class of type A, You can call the method in the implementation class of type A for processing when calling the method in the interface class.
  • Step S204 Determine the corresponding target processor object according to the resource identifier in the resource request, and process the resource request through the target processor object to obtain the model view object.
  • the processor object is an object defined by the business processing layer for processing resource requests, including multiple processing functions, also called processing methods.
  • the processing functions in the processor object process the resource request and return the processing result.
  • the front controller can search for the processor mapper corresponding to the resource request according to the URL in the resource request, and the processor mapper can map the request to the target processor object according to the configuration file or annotation.
  • the model view object (ModelAndView) is used to store the processed result data and the view information used to display the result data.
  • Model represents the model
  • View represents the view.
  • the target processor object processes the resource request, it stores the result data in the model attribute of the model view object, and stores the view information to be returned in the view attribute of the model view object, and then
  • the model view object is returned to the front controller, and the front controller can call the view parser defined in the configuration file to parse the model view object, and display the result data obtained by the analysis on the page specified by the view information.
  • determining the corresponding target processor object according to the resource identifier in the resource request includes: extracting the resource identifier from the resource request; calling the corresponding mapper object according to the resource identifier through the front controller; The processor object obtains the processor object corresponding to the resource request; searches for the processor adapter corresponding to the processor object through the front controller; determines the target processor object from the processor object through the processor adapter.
  • the implementation class that inherits from the default annotation controller mapping processor (DefaultAnnotationHandlerMapping) interface class in the Spring MVC framework can be customized in advance, that is, the custom mapper object (WebSupportHandlerMapping), and the front controller can call the custom
  • the processor acquisition function (getHandler) in the mapper object the processor acquisition function can find the processor object (Handler) and multiple interceptor objects (HandlerInterceptor) through the URL in the resource request, the processor that the mapper object will find
  • the object and multiple interceptor objects are encapsulated into a processor execution chain (HandlerExecuteChain) and returned to the front controller.
  • the front controller traverses all the configured processor adapters and searches for the processing in the processor execution chain from all adapter objects.
  • Handler object (Handler) corresponds to the handler adapter (HandlerAdapter), which calls a specific target handler object from the handler object to process the user's resource request.
  • the front controller before processing the resource request through the target processor object to obtain the model view object, the front controller also calls the preprocessing function (preHandler) in each interceptor object in the execution chain to preprocess the resource request , When it returns false, it means that the whole process of the request is over. When the return value is true, the preprocessing function of the next interceptor object will continue to be called, and when the last interceptor object also returns true, step S206 will be executed to process the resource request through the function in the target processor object.
  • preprocessing function preHandler
  • the target processor object inherits from the same processor interface class; processing the resource request through the target processor object to obtain the model view object includes: obtaining the parameter processing function defined by the processor interface class; The request parameters are passed to the parameter processing function as function parameters, and the model view object corresponding to the resource request returned by the parameter processing function is obtained.
  • the parameter processing function in the processor object can be customized according to business logic.
  • the processor objects corresponding to different resource requests can be different. Different processor objects Can inherit from the same processor interface class or implement the same processor interface.
  • the parameter processing function can be pre-defined in the processor interface class, and the processor object inherited from the processor interface class can be created according to different business logic.
  • the model view object corresponding to the resource request is returned .
  • the step of determining the target processor object adapted to the processor object by the front-end controller specifically includes: the front-end controller traverses all the processor adapters, searches for the processor adapter corresponding to the processor object, and passes The processor adapter calls a specific target processor adapted to the processor object, and processes the user's request through the target processor.
  • the processor object uses the predetermined annotation type @ControllerService to write the properties of the processor object class, and the resource request can be received in the front controller
  • the processor object is automatically obtained according to the context, the corresponding parameter processing function is introduced in the processor object through a custom annotation type, so that the processor object directly references the parameter processing function to process the resource request.
  • Step S206 call the callback function of the interceptor interface class to verify the model view object.
  • the front controller calls the callback function in the interceptor object determined by the mapper object (that is, the function executed after the resource request is processed) to verify the obtained model view object and realize the processing
  • the post-processing of the processor can be processed through the result data or view information in the model view object to check the result data included in the model view object.
  • Step S208 when the callback function returns the code of the exception type, call the exception handling object to process the code of the exception type to obtain a new model view object.
  • Anomaly type codes are unified codes corresponding to respective abnormal information after classification.
  • the implementation class that inherits from the exception handling interface class in the Spring MVC framework can be customized in advance as the exception handling object.
  • the exception handling object WebSupportDispatcherServlet inherits from SimpleMappingExceptionResolver
  • SimpleMappingExceptionResolver is the implementation class of the exception handling interface class HandlerExceptionResolver in the Spring MVC framework.
  • the exception handling object has the processing methods included in the exception handling interface class, and there is no need to repeat coding. Specifically, when the callback function in the interceptor interface class verifies the model view object and returns the exception code type, the processing method included in the exception handling object can be called to process the exception type code to obtain a new model view object.
  • the new model view object includes abnormal information data and view information needed to display the abnormal information corresponding to the abnormal type code.
  • the corresponding exception type will be determined by the interceptor's callback function, and the corresponding exception information will be displayed by returning a new model view object, which can realize the unification of various complex exception information deal with.
  • the above method further includes: obtaining abnormal information and classifying each abnormal information; and encoding according to the type of each abnormal information to obtain the abnormal type code.
  • the exception handling function in the exception handling object can be customized according to the business logic.
  • the exception handling function in the unified exception handling object can be used to process the exception encoding type, and the returned A new model view object that includes abnormal information data.
  • the model view object includes the logical view name and the model data
  • the method further includes: when the callback function does not return the abnormal type code, obtain the view resolution object through the front controller; perform the logical view name through the view resolution object Resolve to obtain the view object; render the model data through the view object to obtain the response data; and return the response data to the client through the front controller.
  • the front controller directly requests the view parser to parse the model view object, obtains the view object, and returns the view object to the front-end control Then, the front controller renders the model data through the view object to obtain the response data, and returns the response data to the client.
  • the client can display the web page according to the response data.
  • Step 210 Generate an abnormal page view object according to the new model view object through the front controller; the abnormal page view object is used to make the client display a page including abnormal information corresponding to the code of the abnormal type.
  • the front controller can call the view analysis object to analyze and obtain the abnormal page view object, and generate response data based on the abnormal page view object and then feed it back to the client.
  • the client can use the response data
  • the included abnormal page view information displays pages including abnormal information.
  • generating the abnormal page view object according to the new model view object through the front controller includes: calling the view resolution object through the front controller; and parsing the logical view name in the new model view object through the view resolution object to obtain Page address; according to the model data and page address in the new model view object, generate the abnormal page view object; return the abnormal page view object to the client, so that the client can render and display according to the abnormal page view object including the code corresponding to the abnormal type Exception information page.
  • the front controller calls the view resolution object and requests the view resolution object to parse the new model view object. After the view resolution object is parsed, the page address is obtained. The page in the page address is used to display the error corresponding to the exception type code Information, the front controller can generate an abnormal page object based on the returned page address and the model data in the new model view object. In this way, the client can render and display the abnormal information corresponding to the type of the abnormality code that occurs according to the abnormal page object. On the page, users can clarify the cause of the exception based on the exception information.
  • the above-mentioned Spring MVC-based exception handling method after the front controller finds the target processor object to process the resource request sent by the client to obtain the model view object, before the model view object is parsed, the interceptor interface class is called through the front controller
  • the callback function verifies the obtained model view object. When the model view object has an exception, it will not pass the verification.
  • the callback function will return the exception type code corresponding to the exception.
  • FIG. 3 it is a schematic diagram of the framework of a Spring MVC-based exception handling method in a specific embodiment.
  • the method specifically includes the following steps:
  • the processor mapper is not found, the corresponding static resource will be obtained according to the resource identifier. If the corresponding static resource cannot be found, a 404 error will be reported;
  • mapping processor maps the request to the execution chain object (HandlerExecutionChain) according to its own configuration or annotation (WebSupportWeb2AppBeanPostProcessor), and returns the execution chain object to the front controller.
  • the execution chain object includes one Handler object (Handler) and multiple interceptor objects (HandlerInterceotor);
  • the front controller traverses all the configured adapters and finds the processor adapter HandlerAdapter corresponding to the processor object;
  • Step 6 will be executed when the method is called and returns true;
  • the processor adapter calls the specific target processor adapted to the processor object, processes the resource request through the target processor, and returns to the model view object (ModelAndView) after the target processor is processed;
  • the front controller passes the new model view object to the view resolver ViewResolver, and the view resolver resolves the logical view name in the new model view object into a specific view object (View) according to the configuration, and returns it to the front controller;
  • the controller renders the incoming model data according to the view object to obtain the response data.
  • a Spring MVC-based exception handling device 400 including: a resource request acquisition module 402, a target processor object acquisition module 404, a model view object acquisition module 406, and a callback The processing module 408 and the exception processing module 410, wherein:
  • the resource request obtaining module 402 is configured to obtain the resource request sent by the client through the front controller;
  • the model view object acquisition module 404 is configured to determine the corresponding target processor object according to the resource identifier in the resource request, and process the resource request through the target processor object to obtain the model view object;
  • the callback processing module 406 is used to call the callback function of the interceptor interface class to verify the model view object
  • the exception handling module 408 is used to call the exception handling object to process the exception type code to obtain a new model view object when the callback function returns the exception type code; generate an exception page view object based on the new model view object through the front controller; the exception page The view object is used to make the client display a page that includes the exception information corresponding to the exception type code.
  • the model view object acquisition module 404 is also used to extract the resource identifier from the resource request; call the corresponding mapper object according to the resource identifier through the front controller; acquire the corresponding resource request through the mapper object Processor object; find the processor adapter corresponding to the processor object through the front controller; determine the target processor object from the processor object through the processor adapter.
  • the target processor object inherits from the same processor interface class; the model view object obtaining module 404 is also used to obtain the parameter processing function defined by the processor interface class; and pass the request parameters in the resource request as function parameters For the parameter processing function, obtain the model view object corresponding to the resource request returned by the parameter processing function.
  • the exception handling object inherits from the same exception handling interface class; the exception handling module 408 is also used to obtain the exception handling function defined by the exception handling interface class; the exception type code is passed to the exception handling function as a function parameter to obtain The new model view object returned by the exception handling function.
  • the exception handling module 408 is also used to call the view resolution object through the front controller; to parse the logical view name in the new model view object through the view resolution object to obtain the page address; according to the new model view object
  • the abnormal page view object is generated from the model data and the page address of the abnormal page view object; the abnormal page view object is returned to the client, so that the client renders and displays the page including the abnormal information corresponding to the abnormal type code according to the abnormal page view object.
  • the model view object includes a logical view name and model data
  • the device further includes a view resolution module.
  • the view resolution module is used to obtain the view resolution object through the front controller when the callback function does not return an abnormal type code;
  • the view resolution object parses the logical view name to obtain the view object; renders the model data through the view object to obtain the response data; and returns the response data to the client through the front controller.
  • the device further includes an anomaly information encoding module, which is used to obtain anomaly information and classify each anomaly information; encode according to the type of each anomaly information to obtain an anomaly type code.
  • an anomaly information encoding module which is used to obtain anomaly information and classify each anomaly information; encode according to the type of each anomaly information to obtain an anomaly type code.
  • the above-mentioned Spring MVC-based exception handling device after finding the target processor object through the front controller to process the resource request sent by the client to obtain the model view object, before parsing the model view object, the interceptor interface class is called through the front controller
  • the callback function verifies the obtained model view object. When the model view object has an exception, it will not pass the verification.
  • the callback function will return the exception type code corresponding to the exception.
  • Each module in the above-mentioned Spring MVC-based exception handling 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. 5.
  • 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 web page resource data.
  • the network interface of the computer device is used to communicate with an external terminal through a network connection.
  • FIG. 5 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied.
  • the specific computer device may Including more or fewer parts than shown in the figure, or combining some parts, or having a different arrangement of parts.
  • the Spring MVC-based exception handling apparatus may be implemented in a form of computer-readable instructions, and the computer-readable instructions may run on the computer device as shown in FIG. 5.
  • the memory of the computer device can store various program modules that make up the Spring MVC-based exception handling device, such as the resource request acquisition module 402, the model view object acquisition module 404, the callback processing module 406, and the exception processing module 408 shown in FIG. 4 .
  • the computer-readable instructions formed by each program module cause the processor to execute the steps in the Spring MVC-based exception handling method of each embodiment of the application described in this specification.
  • the computer device shown in FIG. 5 may execute step S202 through the resource request acquisition module 402 in the Spring MVC-based exception handling apparatus shown in FIG. Z.
  • the computer device may execute step S204 through the model view object acquisition module 404.
  • the computer device can execute step S208 through the callback processing module 406.
  • the computer device may execute step S210 through the exception processing module 408.
  • a computer device includes a memory and one or more processors.
  • the memory stores computer-readable instructions.
  • the one or more processors execute the Spring-based The steps in the exception handling method of MVC.
  • One or more non-volatile computer-readable storage media storing computer-readable instructions.
  • the computer-readable instructions execute the Steps in the exception handling method of Spring MVC.
  • Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • 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.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous chain Channel
  • memory bus Radbus direct RAM
  • RDRAM direct memory bus dynamic RAM
  • RDRAM memory bus dynamic RAM

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne un procédé de gestion d'exceptions basé sur Spring MVC, le procédé consistant à : acquérir, au moyen d'un contrôleur frontal, une demande de ressource envoyée par un client ; déterminer un objet gestionnaire cible correspondant en fonction d'un identificateur de ressource dans la demande de ressource, et gérer la demande de ressource au moyen de l'objet gestionnaire cible pour obtenir un objet de visualisation de modèle ; appeler une fonction de rappel d'une classe d'interface d'interception pour vérifier l'objet de visualisation de modèle ; lorsque la fonction de rappel renvoie un code de type exception, appeler un objet de gestion d'exceptions pour gérer le code de type exception afin d'obtenir un nouvel objet de visualisation de modèle ; et générer un objet de visualisation de page d'exception selon le nouvel objet de visualisation de modèle au moyen du contrôleur frontal, l'objet de visualisation de page d'exception étant utilisé pour permettre au client d'afficher une page comprenant des informations d'exception correspondant au code de type exception.
PCT/CN2019/117506 2019-03-28 2019-11-12 Procédé et appareil de gestion d'exceptions basés sur spring mvc, et dispositif informatique et support de stockage WO2020192134A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910243158.4 2019-03-28
CN201910243158.4A CN110069297B (zh) 2019-03-28 2019-03-28 基于Spring MVC的异常处理方法、装置、计算机设备和存储介质

Publications (1)

Publication Number Publication Date
WO2020192134A1 true WO2020192134A1 (fr) 2020-10-01

Family

ID=67366911

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/117506 WO2020192134A1 (fr) 2019-03-28 2019-11-12 Procédé et appareil de gestion d'exceptions basés sur spring mvc, et dispositif informatique et support de stockage

Country Status (2)

Country Link
CN (1) CN110069297B (fr)
WO (1) WO2020192134A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114579194A (zh) * 2022-03-08 2022-06-03 杭州每刻科技有限公司 一种基于Spring远程调用的异常处理方法和系统

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110069297B (zh) * 2019-03-28 2024-06-28 平安科技（深圳）有限公司 基于Spring MVC的异常处理方法、装置、计算机设备和存储介质
CN110727537B (zh) * 2019-10-21 2023-12-26 深圳前海环融联易信息科技服务有限公司 统一处理响应报文的方法、装置、计算机设备及存储介质
CN111427701A (zh) * 2020-03-09 2020-07-17 中国建设银行股份有限公司 一种工作流引擎系统和业务处理方法
CN111722881B (zh) * 2020-05-22 2023-08-08 广东浪潮大数据研究有限公司 一种容器云平台的资源扩展方法、系统及装置
CN113778726A (zh) * 2020-06-09 2021-12-10 武汉斗鱼网络科技有限公司 一种错误信息处理方法、装置、服务器和存储介质
CN112083952A (zh) * 2020-08-26 2020-12-15 武汉普利商用机器有限公司 一种基于spring架构的异常处理方法及系统
CN112363720B (zh) * 2020-11-30 2024-02-23 中国银行股份有限公司 基于Spring Restful框架实现公共控制逻辑的方法及装置
CN112766769B (zh) * 2021-01-26 2023-11-21 南京利特嘉软件科技有限公司 一种基于大数据的客户评估方法及系统
CN113741870B (zh) * 2021-08-20 2023-07-14 苏州浪潮智能科技有限公司 一种获取Spring框架中数据的方法、系统、设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130007325A1 (en) * 2011-07-01 2013-01-03 Sahita Ravi L Secure handling of interrupted events
CN103955510A (zh) * 2014-04-30 2014-07-30 广西电网公司电力科学研究院 基于etl云平台上传的海量电力营销数据整合方法
CN104317591A (zh) * 2014-10-23 2015-01-28 西安未来国际信息股份有限公司 一种基于OSGi的web界面框架系统及web业务处理方法
CN106484509A (zh) * 2016-09-27 2017-03-08 腾讯科技（深圳）有限公司 一种弹窗的输出方法、装置及终端
CN110069297A (zh) * 2019-03-28 2019-07-30 平安科技（深圳）有限公司 基于Spring MVC的异常处理方法、装置、计算机设备和存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104267944A (zh) * 2014-09-22 2015-01-07 浪潮软件集团有限公司 一种基于Spring的MVC模式优化系统
CN105843609A (zh) * 2016-03-18 2016-08-10 浪潮软件集团有限公司 一种基于Spring和MyBatis的MVC框架
CN105867948A (zh) * 2016-04-26 2016-08-17 江苏物联网研究发展中心 基于AJAX和SpringMVC的WEB开发方法
CN106446023A (zh) * 2016-08-29 2017-02-22 江苏数加数据科技有限责任公司 基于AngularJS和Bootstrap实现的双公示生产数据前端展示系统及方法
CN107172122A (zh) * 2017-03-31 2017-09-15 北京奇艺世纪科技有限公司 一种异常处理方法及装置
CN107590202A (zh) * 2017-08-21 2018-01-16 深圳市华宇兄弟科技股份公司 一种企业平台快速应用的方法及系统
CN107705079A (zh) * 2017-11-08 2018-02-16 厦门旺集信息科技有限公司 物流仓储管理系统处理方法以及跨境电商交易方法
CN108762966A (zh) * 2018-06-05 2018-11-06 中国平安人寿保险股份有限公司 系统异常拦截方法、装置、计算机设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130007325A1 (en) * 2011-07-01 2013-01-03 Sahita Ravi L Secure handling of interrupted events
CN103955510A (zh) * 2014-04-30 2014-07-30 广西电网公司电力科学研究院 基于etl云平台上传的海量电力营销数据整合方法
CN104317591A (zh) * 2014-10-23 2015-01-28 西安未来国际信息股份有限公司 一种基于OSGi的web界面框架系统及web业务处理方法
CN106484509A (zh) * 2016-09-27 2017-03-08 腾讯科技（深圳）有限公司 一种弹窗的输出方法、装置及终端
CN110069297A (zh) * 2019-03-28 2019-07-30 平安科技（深圳）有限公司 基于Spring MVC的异常处理方法、装置、计算机设备和存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114579194A (zh) * 2022-03-08 2022-06-03 杭州每刻科技有限公司 一种基于Spring远程调用的异常处理方法和系统
CN114579194B (zh) * 2022-03-08 2024-04-05 杭州每刻科技有限公司 一种基于Spring远程调用的异常处理方法和系统

Also Published As

Publication number Publication date
CN110069297A (zh) 2019-07-30
CN110069297B (zh) 2024-06-28

Similar Documents

Publication Publication Date Title
WO2020192134A1 (fr) Procédé et appareil de gestion d'exceptions basés sur spring mvc, et dispositif informatique et support de stockage
WO2020151333A1 (fr) Procédé de chargement de page, appareil, dispositif informatique et support d'informations
CN108874926B (zh) 海量数据查询方法、装置、计算机设备和存储介质
CN109344642B (zh) 接口规则校验方法、装置、计算机设备及存储介质
CN109582303B (zh) 通用组件调用方法、装置、计算机设备及存储介质
CN109460527B (zh) 产品数据配置方法、装置、计算机设备和存储介质
CN109474578B (zh) 报文消息校验方法、装置、计算机设备和存储介质
CN109446068B (zh) 接口测试方法、装置、计算机设备和存储介质
CN110209652B (zh) 数据表迁移方法、装置、计算机设备和存储介质
WO2020186786A1 (fr) Procédé et appareil de traitement de fichiers, dispositif informatique et support de stockage
WO2020181839A1 (fr) Procédé de traitement de test de données de page, appareil, dispositif informatique et support de stockage
WO2018184535A1 (fr) Procédé et dispositif de traitement de service d'assurance, serveur et support de stockage
CN111563368A (zh) 报表生成方法、装置、计算机设备和存储介质
CN110109656B (zh) 接口模拟方法、装置、计算机设备和存储介质
CN110908778B (zh) 任务部署方法、系统和存储介质
US11580294B2 (en) Techniques for web framework detection
US10382313B2 (en) Test building for testing server operation
WO2020199594A1 (fr) Procédé et appareil de chargement de composant de service ainsi que dispositif informatique et support de stockage
WO2021120628A1 (fr) Procédé et appareil de détection de mot sensible sur la base d'une chaîne de blocs, dispositif informatique et support de stockage lisible par ordinateur
CN109542764B (zh) 网页自动化测试方法、装置、计算机设备和存储介质
US9026612B2 (en) Generating a custom parameter rule based on a comparison of a run-time value to a request URL
CN115599386A (zh) 代码生成方法、装置、设备及存储介质
CN111901383B (zh) 数据请求处理方法、装置、计算机设备和存储介质
CN116644250B (zh) 页面检测方法、装置、计算机设备和存储介质
US11023426B1 (en) Method and system for detection of open source web application version

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: 19921552

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: 19921552

Country of ref document: EP

Kind code of ref document: A1