io.vertx.up.uca.rs

Interface Filler

All Known Implementing Classes:

ContextFiller, CookieFiller, EmptyFiller, FormFiller, HeaderFiller, PathFiller, QueryFiller, SessionFiller

public interface Filler

「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. In common request workflow, it provide standard key = value attributes into map.
2. For body/stream request workflow, there should be placeholder named EmptyFiller to taken the flow node and then continue for extracting.

For Standard JSR311, it support most parameter annotations and extend JSR311 for business requirement.

Author:

Lang

Field Summary

Fields

Modifier and Type	Field and Description
static Set<Class<? extends Annotation>>	NO_VALUE The type of parameters that will use EmptyFiller for taking place.
static ConcurrentMap<Class<? extends Annotation>,Filler>	PARAMS JSR311 Standard mapping from annotation to Filler component

Method Summary

Modifier and Type	Method and Description
Object	apply(String name, Class<?> paramType, io.vertx.ext.web.RoutingContext datum) The major code logic to get the value of input field name here.

Field Detail

PARAMS

static final ConcurrentMap<Class<? extends Annotation>,Filler> PARAMS

JSR311 Standard mapping from annotation to Filler component

NO_VALUE

static final Set<Class<? extends Annotation>> NO_VALUE

The type of parameters that will use EmptyFiller for taking place.

Method Detail

apply

Object apply(String name,
             Class<?> paramType,
             io.vertx.ext.web.RoutingContext datum)

The major code logic to get the value of input field name here.

Parameters:

name - The parameter name

paramType - The parameter declared type

datum - The RoutingContext of Vert.x ( vertx-web )

Returns:

The extracted value of parameter