Implementing a Chain of Responsibility for an OpenAPI Interface Using Spring and Custom Components

Background: The project provides an OpenAPI interface to upstream systems, containing many functional points such as parameter validation, system configuration checks, data persistence, message sending, etc., with varying client requirements.

Idea: To make each function independent, the chain‑of‑responsibility pattern is used. An abstract class ComponentAbstract.java is created, and each functional point becomes a subclass annotated with @Component("1") (or the default bean name). A custom context class Contxt.java carries data between components, achieving business decoupling.

Execution order is defined beforehand (e.g., stored in a database or Redis) and supplied via a request such as http://localhost:8082/test/chain?index=2,1,3,4 . The controller retrieves each component from the Spring ApplicationContext using AopProxyUtils.getProxyBean and invokes handlerRequest() on it.

Code examples include Maven dependencies, the abstract component, four concrete components (Test1‑Test4), the context class, the Spring utility for obtaining beans, and a test controller LiteFlowController.java that builds the initial context, parses the index order, and runs the chain.

Note: The LiteFlow framework would be a more suitable solution for this scenario, offering friendly documentation and powerful features.