All Classes and Interfaces
Class
Description
Uniform call TunnelClient to remove duplicated codes
Refactor invokder to support Dynamic Invoke
Aeon 桥，用于桥接 Zero / Aeon 容器
Standard verticle deployment.
This component is for @Agent annotated class
Agent scatter to deploy agents
Job manager to manage each job here.
Hunt to aim and select the objective
Mime resolution for web request
1.
Response process to normalize the response request.
This factor could begin following:
1.
This structure is new for `ZeroHttpAgent` extension, you can call this interface to create.
Validation for plug-in api, you can configure the validation
component for api validation in zero-crud module instead of `codex` ( Development )
1.
New Structure for configuration fixed
The configuration data structure:
Future method(I)
Common handler to handle failure
Axis to mount entity
1.
Base class to provide template method
# 「Co」Zero Critical internal failure handler
Common handler to handle failure
「Co」JSR311 for .@CookieParam
This `Filler` is for cookie attributes extracting
FeignDepot to extract the method parameters
Service discovery usage.
Different type for worklow building
「Co」Critical Specific
This `Filler` is placeholder for Body/Stream data in RESTful web request here
In current Filler, it do nothing because the body extracting will go through
`Resolver` for different MIME here.
Codec to transfer envelop
Parameter container to getNull parameters
Help to extract epsilon
Scanned Uri Event ( Metadata ) for each Endpoint.
Scanned @EndPoint clazz to build Event metadata
Start Up condition for different verticle deployment.
Verify special workflow
「Co」Zero for JSR311 Arguments
There are a uniform request flow to get parameters to support JSR311 in zero framework, here I defined **Filler**
interface ( Fill argument into container, it's specific component )
1.
Filter processing
path = Event Chain
「Co」JSR311 for .@FormParam
This `Filler` is for form attributes extracting
Future method(Envelop)
## Reference Calculation
### 1.
「Atom Internal」Atom Internal Channel Usage
「Co」JSR311 for .@HeaderParam
This `Filler` is for header map `key=value` extract such as
```shell
//
「环境工厂」
静态环境工厂专用方法，替换原始的 Highway 部分的连接，并且从接口中剥离出来，可直接调用
Mix Atom Load for different HAtom Loading
HPerformer<T extends io.horizon.specification.modeler.HModel>
QBE专用流程，解析 QBE 参数
This factor could begin following:
1.
Hub management for route
# 「Co」Zero Framework for MIME parsing
Incoming message for request
Infix initialization
Package scanner
Replier for method invoking
Tool for invoker do shared works.
This class is for @Ipc and @Address must be in @Queue class instead of other specification.
Deprecated.
JobStore bridge for Set get
1) @Job annotation class here
2) Database job store here that configured in vertx-job.yml
Json Resolver
Deprecated.
M/U means modal unit, its format is following, please refer the related definition.yml file and definition.json
file for more details of KClass structure.
Launcher:
1.
Hub for mime type
Producer/Consumer
register to route to generate mime support
void method(Messsage)
Vertx Application begin launcher for api gateway.
# 「Co」Zero Mime Processing here
This component will process the request data before your code occurs
Data Object to describe job detail, it stored job definition
1) The definition came from scanned @Job annotation class ( each class should has one Mission )
2) The definition came from JobStore interface ( the job definition may be stored into database or other
Splitter to getNull executor reference.
Micro service mode only, Fix for http endpoint part
This atom is a standard implementation because of all the attributes is static and fixed, you can not configure
all the information when the container is running, this model will connect to `pojo/{0}.yml` file ( It's internal
mapping Channel ) and capture the `Mu` definition for current static model.
OneWayAim: Event Bus: One-Way
「Co」JSR311 for .@PathParam
This `Filler` is for path parsing `/api/xxx/name/{name}` format to extract to
```shell
//
BlockAim: Non-Event Bus: One-Way
void method(Envelop)
void method(Envelop)
「Extension」:
Name: Auditor System
Extension for auditing system in zero system
This sub system often happened before each Worker component.
「Extension」
Name: Data Region
Data Region when you want to do some modification on Envelop,
There are two position to process region modification:
1) Before Envelop request building & sending.
「Extension」
Name: Etcd Registry Extension
This plugin is required when you enabled zero-crud extension.
Router mounter for api gateway.
「Co」JSR311 for .@QueryParam
This `Filler` is for query string `/api/xxx?name={name}` format to extract to
```shell
//
This class is For annotation @Queue scanning
It will scan all classes that annotated with @Queue, zero system
will extract worker class from this scanned classes.
Verification for epsilon
The Cache Key Definition
Scanned address ( Metadata ) for Queue.
Scanned @Queue clazz to build Receipt metadata
Receipt annotation inquirer
This thread is for Receipt extraction
This worker is for @WebSocket annotation to configure the active sending message
for alert ( Internal WebSite Message )
# 「Co」Zero Resolver
The interface that zero provide for request content resolving for
1.
Rpc parameter, getNull data from remote
Child component works
JSR330 signal
Validation for request based on JSR303 Bean Validation
1.
# 「Co」Zero Solve
This component will be called by specific `Resolver` internally.
Major execution to verify the result.
SyncAim: Non-Event Bus: Request-Response
Envelop method(Envelop)
「Co」Resolver default class
It's placeholder to compared in resolver selector workflow.
Hub for Uri basic
path, method, order
register to route to generate mime support
This object is for uri store, it could store following information
1.
#「Kt」Utility X Component in zero
Inner class of `Jooq` tool of Jooq Engine operations based on pojo here.
Shared Data for pool usage in utility X
Vertx Application entry
1) VertxApplication: start up zero framework in `application` mode.
Talk holder for set default user.
Secure mount
401 for authorization only
This class is for @Wall of security here.
「Co」Zero Framework
Here I added new configuration `freedom` to zero framework as critical data specification here for
old system integration here.
Worker verticle deployment
Worker scatter to deploy workers
ZaaS -> Zero Authenticate and Authorization Service
Interface defined for component
Transfer Class<?> set to difference mapping.
Starter of 3 Applications
- VertxApplication ( Standard )
- MicroApplication ( Legacy Micro Service )
- AeonApplication ( Native Cloud )
Arcane:神秘的，秘密的
Zero新版启动器，将启动周期直接从ZeroHeart中拿掉，统一规划启动，ZeroHeart只负责判断
Resource ZeroPack for yml configuration, Loaded once
Default Http Server agent for router handlers.
Get data from event bus and push metadata to Etcd.
Default Http Server worker for different handler.
Start up tools shared in
Web Application & Rx Application
Background worker of Zero framework, it's for schedule of background tasks here.
# 「Error」Zero Exception
* Category: WebException
* Code: -60052
* Status: 411
# 「Error」Zero Exception
* Category: WebException
* Code: -60053
* Status: 415