CN110990076A - Hot plug component chain calling method based on responsibility chain mode - Google Patents
Hot plug component chain calling method based on responsibility chain mode Download PDFInfo
- Publication number
- CN110990076A CN110990076A CN201911138427.7A CN201911138427A CN110990076A CN 110990076 A CN110990076 A CN 110990076A CN 201911138427 A CN201911138427 A CN 201911138427A CN 110990076 A CN110990076 A CN 110990076A
- Authority
- CN
- China
- Prior art keywords
- component
- chain
- calling
- configuration
- steps
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
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/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
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
The invention relates to a hot-plug component chain calling method based on a responsibility chain mode, which is characterized in that a plurality of hot-plug components are configured on a persistent layer, the configuration of the persistent layer is scanned and loaded into a memory after a Spring container is started, when an upstream service processing request is obtained, critical resources of data needing to be processed are checked, the locked critical resources are skipped, the usable critical resources are locked, corresponding configuration information in the memory is obtained, a component chain is called, if the calling is successful, the components in the component chain are configured and called one by one, the lock on the critical resources is released finally, and the message processing is finished. The invention modularizes the service chain, improves code reusability and engineering capability, ensures the consistency of data in a mode of mixing a local transaction manager and a compensation type transaction, and can be changed emergently on the premise of not stopping engineering, thereby achieving the purpose of hot plug; the service chain takes the responsibility chain as a core, the debugging and the problem searching become simple, and the specified component can be repaired.
Description
Technical Field
The invention belongs to the technical field of digital information transmission, such as telegraph communication, and particularly relates to a hot plug component chain calling method realized based on a responsibility chain mode for a transmission control procedure, such as a data link level control procedure.
Background
With the coming of the internet era, people's offline lives gradually tend to be online, and it is a great challenge for engineers responsible for online implementation to face business needs that need to change at any time.
In the prior art, for engineering personnel, codes are frequently modified and redeployed according to new business requirements in a traditional mode, namely, the codes are developed according to requirements in a customized mode, and positions needing to be developed and modified are only developed and modified according to the requirements, so that the experience is poor for customers, and development resources are wasted.
To reduce the workload of engineers while maintaining customer experience, a technique is needed to implement changes in processing logic dynamically through a few persistent layer configurations, including databases or XML, based on business changes and new requirements.
Disclosure of Invention
The invention solves the problems of poor customer experience and development resource waste caused by frequent code modification and redeployment according to new service requirements in the prior art, and provides an optimized hot plug component chain calling method based on a responsibility chain mode.
The technical scheme adopted by the invention is that a hot plug component chain calling method based on a responsibility chain mode is realized, and the method comprises the following steps:
step 1: configuring a plurality of pluggable components in a persistent layer;
step 2: starting a Spring container, scanning the configuration of the persistence layer and loading the configuration into a memory;
and step 3: if an upstream service processing request is obtained, the next step is carried out, otherwise, the step 3 is repeated;
and 4, step 4: checking critical resources of data to be processed, skipping the locked critical resources, and locking the critical resources to perform the next step if the locked critical resources are not locked;
and 5: acquiring corresponding configuration information in a memory, and calling a component chain; if the calling is successful, the next step is carried out, otherwise, the step 7 is carried out;
step 6: carrying out successive configuration and calling on the components in the component chain;
and 7: releasing the lock applied to the critical resource and ending the message processing.
Preferably, in the step 1, the configured content includes an execution sequence of pluggable components in the component chain and corresponding component instance names.
Preferably, in step 2, the configuration includes table configuration or XML file of the database, and when the configuration content is updated, the memory is refreshed and the execution sequence of all pluggable components is adjusted.
Preferably, in step 5, the configuration information is a mapping relationship between a request or a message type and a component chain configuration.
Preferably, in step 5, the instance is reinitialized in the calling process.
Preferably, the step 6 comprises the steps of:
step 6.1: taking a first component in the component chain according to the priority;
step 6.2: if the current component is a remote component, carrying out remote component calling, and carrying out the step 6.4, otherwise, carrying out the next step;
step 6.3: acquiring an instance of a current component from a Spring container, and calling the component;
step 6.4: if the calling is unsuccessful, carrying out corresponding processing and carrying out the step 7, otherwise, carrying out the next step;
step 6.5: if the next component exists, the next component is the current component, and step 6.2 is performed, otherwise, the request processing is completed, and step 7 is performed.
Preferably, in step 6.2, the remote component call comprises the following steps:
step 6.2.1: setting the retry number upper limit as 0;
step 6.2.2: constructing a corresponding request agent class according to the type of the request;
step 6.2.3: sending a request, and synchronously acquiring a request result;
step 6.2.4: based on the request result, if the remote request is completed or the retry number upper limit is reached, the call is unsuccessful, and step 6.4 is performed, otherwise, the next step is performed;
step 6.2.5: the number of retries is incremented by 1 and step 6.2.3 is performed.
Preferably, said step 6.3 comprises the steps of:
step 6.3.1: performing parameter assembly according to the configuration information;
step 6.3.2: acquiring an instance of the component through the context in the Spring container;
step 6.3.3: executing a method for processing service logic, and waiting for an obtained execution result;
step 6.3.4: the component is invoked.
Preferably, in step 6.4, the corresponding processing includes:
if the current component is a non-remote component and the calling is unsuccessful, an unprocessed exception exists, the transaction is triggered to roll back, the local transaction is directly handed to the transaction manager to roll back, and the step 7 is carried out;
if the current component is a remote component and the calling is unsuccessful, calling a compensation type transaction method in the same component, and rolling back all completed component transactions in reverse sequence.
Preferably, the settings specify the thread timing to scan the configuration table or XML file, and when a change occurs, an event is triggered to reload the configuration file.
The invention provides an optimized hot-plug component chain calling method based on a responsibility chain mode, which is characterized in that a plurality of hot-plug components are configured on a persistent layer, the configuration of the persistent layer is scanned and loaded into a memory after a Spring container is started, when an upstream service processing request is obtained, critical resources of data needing to be processed are checked, the locked critical resources are skipped, the usable critical resources are locked, corresponding configuration information in the memory is obtained, a component chain is called, if the calling is successful, the components in the component chain are configured and called one by one, the lock on the critical resources is released finally, and the message processing is finished.
In the invention, the data consistency problem is solved by configuring the execution sequence of the component chain and the instance names of the components in the persistent layer, ensuring local transactions through the local transaction manager and ensuring remote transactions through compensation type transactions, executing corresponding components according to the configuration in a dynamic proxy mode, and realizing hot plug of processing components according to the requirement and the change of a service model.
The invention divides the complex project into a plurality of single components, modularizes the service chain, improves the code reusability and the project capability, only needs a little configuration, the rest work can be automatically completed, and the engineer only needs to code each basic component; the consistency of data is ensured in a mode of mixing a local transaction manager and a compensation type transaction, and the data is called in a dynamic proxy mode; the whole service chain is modularized, engineering personnel pay attention to the extraction and decoupling of codes, the processing of a calling process and a result is handed to an agent class executed by the components, service change and addition are that some components are newly added or modified for engineering, and the emergency change can be carried out on the premise that the engineering is not stopped, so that the purpose of hot plug is achieved; the whole service chain takes a responsibility chain design mode as a core, the debugging and the problem searching become simple, and the specified component can be repaired.
Drawings
FIG. 1 is a flow chart of the present invention.
Detailed Description
The present invention is described in further detail with reference to the following examples, but the scope of the present invention is not limited thereto.
The invention relates to a hot plug component chain calling method based on a responsibility chain mode. The responsibility chain mode is a Java design mode, a receiver is a complete processing chain when a requester sends a request, the receiver is essentially a component chain, all components need to realize specific interfaces, and the whole processing flow forms the responsibility chain mode and is not coupled with each other; after the pluggable components are decoupled from actual services according to requirements, the generated processing logic needs no coupling among the components.
The method comprises the following steps.
Step 1: and configuring a plurality of pluggable components in the persistence layer.
In step 1, the configured content includes an execution sequence of pluggable components in the component chain and corresponding component instance names.
In the invention, in the configuration table or XML of the configuration, a part of code fragments capable of being compiled into classes, such as Groovy code fragments, are allowed to be used, and temporary components are created through reflection to be called.
In the invention, the configured logic is the execution logic of the service, and comprises the file position, the type, the execution priority and the like of the configured component, wherein the priority order refers to the execution order of the component, and can also be directly declared on the Java component in an annotation way.
In the invention, any service firstly realizes the self-configured component chain, namely realizes the self-configured service logic, and the execution sequence is determined when the self-configured component chain is realized, so the self-configured component chain is displayed in a configuration file, XML or a persistent layer configuration mode.
In the invention, the configuration is mainly used for specifying the path of the class to be dynamically proxied by the proxy class and the type and the execution sequence of other languages, if the proxy class is the REST API, the address, the retry times, the protocol type and the like of the API need to be specified, and the configuration can ensure that long service codes which are decoupled by programmers or are split into fragmented components according to services can be executed according to the set sequence, thereby achieving the same effect of a single long service code.
Step 2: and starting a Spring container, scanning the configuration of the persistence layer and loading the configuration into the memory.
In step 2, table configuration or XML file including database is configured, and when the configuration content is updated, the memory is refreshed and the execution sequence of all pluggable components is adjusted.
Setting a designated thread to scan the configuration table or XML file at regular time, and triggering an event to reload the configuration file when a change occurs.
In the invention, the Spring container is started, the database or the configuration file of the XML is scanned, and the corresponding component chain calling mode and the corresponding transaction control mode of each service are loaded into the memory, so that the performance is prevented from being influenced by calling from the persistent layer every time.
In the invention, in the process of starting and loading the configuration of the persistent layer by the Spring container, a lazy loading mode can be adopted when the number of the components is too much, the components are loaded when the instance is automatically injected, the configured part is loaded into the memory after the loading is finished, and the cache is refreshed when the configuration file is changed or the configuration of the database is changed, thereby adjusting the execution sequence of the components; but since the components use a lazy load and initialize instance, the instance needs to be reinitialized when called to improve performance.
In the invention, when the change occurs, the configuration file is reloaded by the triggering event, and the configuration table or the XML file is scanned at regular time by the appointed thread, so that the calling configuration of the component chain can be adjusted under the condition of no shutdown of the project.
In the invention, when an upstream system initiates a request to the core service processing responsibility chain, an agent class executed by a component can take out a component list and an execution sequence for processing the service from a memory, at the moment, a critical resource at the upstream needs to be locked, the agent class can sequentially call each component, when uncaptured abnormity occurs, a transaction rollback mode in a configuration file is called, the default is local transaction, a transaction manager is called to rollback the transaction, if the uncaptured abnormity occurs, a compensation type transaction in each component is called to rollback the transaction, and when all components are normally taken away or all the transactions are played by abnormal rollback. Releasing the critical resources. The method comprises the following specific steps.
And step 3: and (4) if the upstream service processing request is obtained, carrying out the next step, otherwise, repeating the step (3).
And 4, step 4: and checking the critical resources of the data to be processed, skipping the locked critical resources, and locking the critical resources to perform the next step if the locked critical resources are not locked.
In the invention, when an upstream service processing request, such as an MQ message or a request comes, critical resources of data to be processed are checked, if the critical resources are locked, other components are proved to be processed, and skipping is carried out, otherwise, locking is carried out to enter a processing part.
In the invention, the thread of the dynamic agent execution component chain is taken from a thread pool started along with the project, part of the critical resource is from the interior of the project, more critical resources are from the interior of the thread pool for robbing, and when the working thread is saturated, namely no resource is used for processing a new request, the new request enters a waiting queue or is directly handed over to a user thread for processing.
In the invention, the locked resource is an internal resource of the execution thread, when the locking fails, the thread is proved to be processing, namely processing the next request, and the locking part is an overtime lock, so that the situation that the thread is always blocked due to network reasons when the internal part of the component is realized or the REST API is called is prevented.
In the invention, the failure is regarded as failure when the time slice is not finished, the critical resource is released, and the feedback is carried out through the log.
And 5: acquiring corresponding configuration information in a memory, and calling a component chain; and if the calling is successful, performing the next step, otherwise, performing the step 7.
In step 5, the configuration information is a mapping relationship between a request or a message type and a component chain configuration.
In the step 5, the instance is reinitialized in the calling process.
In the invention, the processing mode of the request or MQ message of the type is acquired from the cache, the mapping relation between the request or the message type and the configuration of the component execution chain is stored in the cache, the following steps are continuously executed when the configuration information of the component chain is acquired, otherwise, the exception is thrown out, and the critical resource lock is released. The processing procedure is ended.
Step 6: successive configurations and calls are made to components in the chain of components.
The step 6 comprises the following steps:
step 6.1: taking a first component in the component chain according to the priority;
step 6.2: if the current component is a remote component, carrying out remote component calling, and carrying out the step 6.4, otherwise, carrying out the next step;
in step 6.2, the remote component invocation comprises the following steps:
step 6.2.1: setting the retry number upper limit as 0;
step 6.2.2: constructing a corresponding request agent class according to the type of the request;
step 6.2.3: sending a request, and synchronously acquiring a request result;
step 6.2.4: based on the request result, if the remote request is completed or the retry number upper limit is reached, the call is unsuccessful, and step 6.4 is performed, otherwise, the next step is performed;
step 6.2.5: the number of retries is incremented by 1 and step 6.2.3 is performed.
Step 6.3: acquiring an instance of a current component from a Spring container, and calling the component;
said step 6.3 comprises the steps of:
step 6.3.1: performing parameter assembly according to the configuration information;
step 6.3.2: acquiring an instance of the component through the context in the Spring container;
step 6.3.3: executing a method for processing service logic, and waiting for an obtained execution result;
step 6.3.4: the component is invoked.
Step 6.4: if the calling is unsuccessful, carrying out corresponding processing and carrying out the step 7, otherwise, carrying out the next step;
in step 6.4, the corresponding processing includes:
if the current component is a non-remote component and the calling is unsuccessful, an unprocessed exception exists, the transaction is triggered to roll back, the local transaction is directly handed to the transaction manager to roll back, and the step 7 is carried out;
if the current component is a remote component and the calling is unsuccessful, calling a compensation type transaction method in the same component, and rolling back all completed component transactions in reverse sequence.
Step 6.5: if the next component exists, the next component is the current component, and step 6.2 is performed, otherwise, the request processing is completed, and step 7 is performed.
In the invention, the components in the component chain have execution sequences, and if engineering personnel extract various components according to service dimensions, the components need to be executed according to the priority of the configured component execution sequence, thereby ensuring the accuracy of service logic.
In the invention, after the configuration information of the component chain is acquired, the agent class executes the number of times of failure retry according to the configuration information, such as the path or bean name of the component, and certainly, the agent class does not retry by default; after the parameters are assembled by the proxy class, the method for processing the service logic is executed by acquiring the instance of the component through the context of the Spring IOC container, and the part is synchronous execution, namely waiting to acquire the execution result.
In the invention, if the component is a remote REST API, a corresponding request agent class is constructed according to the type of the request, the request is sent, and the result of the request is synchronously obtained, so that whether the remote request is finished or not is judged; the number of failed retries may be declared in the configuration file because the interface call may be limited to the network environment.
In the present invention, when the complete chain of components is executed and no exception is thrown, the request processing is completed and the critical resource lock is released.
In the invention, when unprocessed exception occurs, rollback of the transaction is triggered; directly submitting the local affair to the affair manager for rolling back, releasing the critical resource lock and returning a processing result; if the transaction is a remote transaction, the method of the compensation type transaction in the same component needs to be called when the rollback is carried out, which is realized by the remote component, and the rollback of all completed component transactions is completed in reverse sequence.
In the invention, specifically, the remote API calling mode may be retried according to the configured times because of the occurrence of 404 and other states of a network reason or an opposite terminal interface reason, and the remote calling result is obtained within a tolerable range to the maximum extent; when the remote calling is successful, calling subsequent configured components, retrying when 404 occurs, executing a rollback transaction when the retry times reach a preset value or directly reporting errors, and recording a log.
And 7: releasing the lock applied to the critical resource and ending the message processing.
The invention configures a plurality of pluggable components in a persistent layer, scans the configuration of the persistent layer after starting a Spring container and loads the configuration into a memory, when an upstream service processing request is obtained, checks the critical resource of data to be processed, skips the locked critical resource, locks the usable critical resource, acquires the corresponding configuration information in the memory, calls a component chain, and if the calling is successful, the components in the component chain are configured and called one by one, finally releases the lock on the critical resource, and the message processing is finished.
In the invention, the data consistency problem is solved by configuring the execution sequence of the component chain and the instance names of the components in the persistent layer, ensuring local transactions through the local transaction manager and ensuring remote transactions through compensation type transactions, executing corresponding components according to the configuration in a dynamic proxy mode, and realizing hot plug of processing components according to the requirement and the change of a service model.
The invention divides the complex project into a plurality of single components, modularizes the service chain, improves the code reusability and the project capability, only needs a little configuration, the rest work can be automatically completed, and the engineer only needs to code each basic component; the consistency of data is ensured in a mode of mixing a local transaction manager and a compensation type transaction, and the data is called in a dynamic proxy mode; the whole service chain is modularized, engineering personnel pay attention to the extraction and decoupling of codes, the processing of a calling process and a result is handed to an agent class executed by the components, service change and addition are that some components are newly added or modified for engineering, and the emergency change can be carried out on the premise that the engineering is not stopped, so that the purpose of hot plug is achieved; the whole service chain takes a responsibility chain design mode as a core, the debugging and the problem searching become simple, and the specified component can be repaired.
Claims (10)
1. A hot plug component chain calling method based on responsibility chain mode is characterized in that: the method comprises the following steps:
step 1: configuring a plurality of pluggable components in a persistent layer;
step 2: starting a Spring container, scanning the configuration of the persistence layer and loading the configuration into a memory;
and step 3: if an upstream service processing request is obtained, the next step is carried out, otherwise, the step 3 is repeated;
and 4, step 4: checking critical resources of data to be processed, skipping the locked critical resources, and locking the critical resources to perform the next step if the locked critical resources are not locked;
and 5: acquiring corresponding configuration information in a memory, and calling a component chain; if the calling is successful, the next step is carried out, otherwise, the step 7 is carried out;
step 6: carrying out successive configuration and calling on the components in the component chain;
and 7: releasing the lock applied to the critical resource and ending the message processing.
2. The method according to claim 1, wherein the method comprises the following steps: in step 1, the configured content includes an execution sequence of pluggable components in the component chain and corresponding component instance names.
3. The method according to claim 1, wherein the method comprises the following steps: in step 2, table configuration or XML file including database is configured, and when the configuration content is updated, the memory is refreshed and the execution sequence of all pluggable components is adjusted.
4. The method according to claim 1, wherein the method comprises the following steps: in step 5, the configuration information is a mapping relationship between a request or a message type and a component chain configuration.
5. The method according to claim 1, wherein the method comprises the following steps: in the step 5, the instance is reinitialized in the calling process.
6. The method according to claim 1, wherein the method comprises the following steps: the step 6 comprises the following steps:
step 6.1: taking a first component in the component chain according to the priority;
step 6.2: if the current component is a remote component, carrying out remote component calling, and carrying out the step 6.4, otherwise, carrying out the next step;
step 6.3: acquiring an instance of a current component from a Spring container, and calling the component;
step 6.4: if the calling is unsuccessful, carrying out corresponding processing and carrying out the step 7, otherwise, carrying out the next step;
step 6.5: if the next component exists, the next component is the current component, and step 6.2 is performed, otherwise, the request processing is completed, and step 7 is performed.
7. The method according to claim 6, wherein the method comprises the following steps: in step 6.2, the remote component invocation comprises the following steps:
step 6.2.1: setting the retry number upper limit as 0;
step 6.2.2: constructing a corresponding request agent class according to the type of the request;
step 6.2.3: sending a request, and synchronously acquiring a request result;
step 6.2.4: based on the request result, if the remote request is completed or the retry number upper limit is reached, the call is unsuccessful, and step 6.4 is performed, otherwise, the next step is performed;
step 6.2.5: the number of retries is incremented by 1 and step 6.2.3 is performed.
8. The method according to claim 6, wherein the method comprises the following steps: said step 6.3 comprises the steps of:
step 6.3.1: performing parameter assembly according to the configuration information;
step 6.3.2: acquiring an instance of the component through the context in the Spring container;
step 6.3.3: executing a method for processing service logic, and waiting for an obtained execution result;
step 6.3.4: the component is invoked.
9. The method according to claim 6, wherein the method comprises the following steps: in step 6.4, the corresponding processing includes:
if the current component is a non-remote component and the calling is unsuccessful, an unprocessed exception exists, the transaction is triggered to roll back, the local transaction is directly handed to the transaction manager to roll back, and the step 7 is carried out;
if the current component is a remote component and the calling is unsuccessful, calling a compensation type transaction method in the same component, and rolling back all completed component transactions in reverse sequence.
10. The method according to claim 1, wherein the method comprises the following steps: setting a designated thread to scan the configuration table or XML file at regular time, and triggering an event to reload the configuration file when a change occurs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911138427.7A CN110990076A (en) | 2019-11-20 | 2019-11-20 | Hot plug component chain calling method based on responsibility chain mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911138427.7A CN110990076A (en) | 2019-11-20 | 2019-11-20 | Hot plug component chain calling method based on responsibility chain mode |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110990076A true CN110990076A (en) | 2020-04-10 |
Family
ID=70085221
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911138427.7A Pending CN110990076A (en) | 2019-11-20 | 2019-11-20 | Hot plug component chain calling method based on responsibility chain mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990076A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112306575A (en) * | 2020-10-30 | 2021-02-02 | 常州微亿智造科技有限公司 | Industrial quality inspection picture verification method and device |
| CN113312039A (en) * | 2021-06-25 | 2021-08-27 | 武汉众邦银行股份有限公司 | Method and device for constructing responsibility tree mode universal code framework |
| CN113377350A (en) * | 2021-06-29 | 2021-09-10 | 中国平安财产保险股份有限公司 | Access request processing method, device, equipment and readable storage medium |
| CN113515322A (en) * | 2021-06-29 | 2021-10-19 | 平安养老保险股份有限公司 | Application program loading method and device, computer equipment and readable storage medium |
| CN113760487A (en) * | 2020-08-05 | 2021-12-07 | 北京京东振世信息技术有限公司 | Service processing method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020108099A1 (en) * | 2000-10-11 | 2002-08-08 | Charles Paclat | Method for developing business components |
| CN103605526A (en) * | 2013-11-28 | 2014-02-26 | 蓝盾信息安全技术股份有限公司 | Template componentized code generating method based on chain-of-responsibility pattern |
| CN104268024A (en) * | 2014-09-24 | 2015-01-07 | 浪潮(北京)电子信息产业有限公司 | Method and device for achieving process mutual exclusion |
| CN106656622A (en) * | 2016-12-29 | 2017-05-10 | 深圳Tcl新技术有限公司 | Method and device for configuring interface call tasks |
| US20170249171A1 (en) * | 2016-02-25 | 2017-08-31 | Brocade Communications Systems, Inc. | Runtime Configuration of Servlet Filtering Using Dynamic Injection |
| CN108712456A (en) * | 2018-03-27 | 2018-10-26 | 上海淘票儿信息科技有限公司 | Network interaction method, equipment and system |
-
2019
- 2019-11-20 CN CN201911138427.7A patent/CN110990076A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020108099A1 (en) * | 2000-10-11 | 2002-08-08 | Charles Paclat | Method for developing business components |
| CN103605526A (en) * | 2013-11-28 | 2014-02-26 | 蓝盾信息安全技术股份有限公司 | Template componentized code generating method based on chain-of-responsibility pattern |
| CN104268024A (en) * | 2014-09-24 | 2015-01-07 | 浪潮(北京)电子信息产业有限公司 | Method and device for achieving process mutual exclusion |
| US20170249171A1 (en) * | 2016-02-25 | 2017-08-31 | Brocade Communications Systems, Inc. | Runtime Configuration of Servlet Filtering Using Dynamic Injection |
| CN106656622A (en) * | 2016-12-29 | 2017-05-10 | 深圳Tcl新技术有限公司 | Method and device for configuring interface call tasks |
| CN108712456A (en) * | 2018-03-27 | 2018-10-26 | 上海淘票儿信息科技有限公司 | Network interaction method, equipment and system |
Non-Patent Citations (5)
| Title |
|---|
| HUHAHUHA_: "Spring之-SpringIoC容器与Bean的装配，huhahuha_,https://blog.csdn.net/huhahuha_/article/details/82690113", 《SPRING之-SPRINGIOC容器与BEAN的装配，HUHAHUHA_，20180916》 * |
| JAVA道⼈: "springboot进行热插拔，JAVA道人，springboot进行热插拔，20190426", 《SPRINGBOOT进行热插拔，JAVA道人，SPRINGBOOT进行热插拔，20190426》 * |
| 周倩: "基于微服务架构的分享活动***的设计与实现", 《基于微服务架构的分享活动***的设计与实现》 * |
| 甜菜波波: "Spring Cloud重试机制与各组件的重试总结，甜菜波波，https://www.cnblogs.com/tiancai/p/9583942.html", 《SPRING CLOUD重试机制与各组件的重试总结，甜菜波波，20180904》 * |
| 编程家阿笨猫: "https://blog.csdn.net/hong0220/article/details/50496368", 《SPRINGBOOT在ECLIPSESTS设置热插拔免重启 编程家阿笨猫 20160111》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113760487A (en) * | 2020-08-05 | 2021-12-07 | 北京京东振世信息技术有限公司 | Service processing method and device |
| CN113760487B (en) * | 2020-08-05 | 2024-04-12 | 北京京东振世信息技术有限公司 | Service processing method and device |
| CN112306575A (en) * | 2020-10-30 | 2021-02-02 | 常州微亿智造科技有限公司 | Industrial quality inspection picture verification method and device |
| CN113312039A (en) * | 2021-06-25 | 2021-08-27 | 武汉众邦银行股份有限公司 | Method and device for constructing responsibility tree mode universal code framework |
| CN113377350A (en) * | 2021-06-29 | 2021-09-10 | 中国平安财产保险股份有限公司 | Access request processing method, device, equipment and readable storage medium |
| CN113515322A (en) * | 2021-06-29 | 2021-10-19 | 平安养老保险股份有限公司 | Application program loading method and device, computer equipment and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110990076A (en) | Hot plug component chain calling method based on responsibility chain mode | |
| CN109542639B (en) | Processing method and processing device for guaranteeing consistency of microservice calling data | |
| US8762929B2 (en) | System and method for exclusion of inconsistent objects from lifecycle management processes | |
| US20020161840A1 (en) | Adapter for interfacing with a workflow engine | |
| US8689179B2 (en) | Transportable refactoring object | |
| US6253257B1 (en) | Software Interface for dynamic API mapping | |
| US8676635B2 (en) | Method and system for managing transactions | |
| US7941703B2 (en) | Capturing machine state of unstable java program | |
| JPH03504175A (en) | data processing network | |
| US20070285993A1 (en) | Systems and methods for common instance handling of providers in a plurality of frameworks | |
| US20050268238A1 (en) | Application server configuration tool | |
| US6141679A (en) | High performance distributed transaction processing methods and apparatus | |
| US8924947B2 (en) | Direct deployment of static content | |
| CN109525436B (en) | Method and system for switching main application program and standby application program | |
| CN111625323A (en) | Distributed task processing method, device, equipment and computer readable storage medium | |
| Cisco | Troubleshooting the SNA View Mainframe Application | |
| Cisco | Troubleshooting the SNA View Mainframe Application | |
| Cisco | Troubleshooting SNA View on the Workstation | |
| Cisco | Troubleshooting SNA View on the Workstation | |
| Cisco | Troubleshooting SNA View on the Workstation | |
| Cisco | Troubleshooting SNA View on the Workstation | |
| Cisco | Troubleshooting SNA View on the Workstation | |
| Cisco | Troubleshooting SNA View on the Workstation | |
| Cisco | Troubleshooting SNA View on the Workstation | |
| Cisco | Troubleshooting the SNA View Mainframe Application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200410 |
|
| RJ01 | Rejection of invention patent application after publication |