Interface FilterOrder
public interface FilterOrder
The filtering pipeline consists of a number of distinct phases. Filters can
indicate when and where they should be applied in the pipeline using the
Priority annotation.
Each phase of the filtering pipeline is bound to a different
Priority.ring(). These phases are enumerated below:
STREAMINGfilters are applied first and are used to manipulate the content of the request or response, for example to apply compression to responsesURL_MAPPINGfilters are applied next, and are used to map the request to a particular backing store, for example to map a request to a particular schema in a particular database. This is a crucial phase as subsequent phases are dependent on this phase, for example theAUTHENTICATIONphase often depends on this phase in order to be able to determine what database to check credentials against.AUTHENTICATIONfilters examine any credentials in the request and maps them to aPrincipaland roles.RETARGETTINGfilters examine a request and re-write the request so that it is dispatched to a different request URL. This is similar tomod_rewritein Apache, requests are examined and potentially re-targeted to different dispatchers depending on values in the request URL and/or request headers.DISPATCHINGis the final phase, where a decision is made about which servlet will service the request
- Author:
- cdivilly
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final intAUTHENTICATIONfilters examine any credentials in the request and maps them to aPrincipaland roles.static final intDISPATCHINGis the final phase, where a decision is made about which servlet will service the requeststatic final intRETARGETTINGfilters examine a request and re-write the request so that it is dispatched to a different request URL.static final intSTREAMINGfilters are applied first and are used to manipulate the content of the request or response, for example to apply compression to responses.static final intURL_MAPPINGfilters are applied next, and are used to map the request to a particular backing store, for example to map a request to a particular schema in a particular database.
-
Field Details
-
STREAMING
static final int STREAMINGSTREAMINGfilters are applied first and are used to manipulate the content of the request or response, for example to apply compression to responses.- See Also:
-
URL_MAPPING
static final int URL_MAPPINGURL_MAPPINGfilters are applied next, and are used to map the request to a particular backing store, for example to map a request to a particular schema in a particular database. This is a crucial phase as subsequent phases are dependent on this phase, for example theAUTHENTICATIONphase often depends on this phase in order to be able to determine what database to check credentials against.- See Also:
-
AUTHENTICATION
static final int AUTHENTICATIONAUTHENTICATIONfilters examine any credentials in the request and maps them to aPrincipaland roles.- See Also:
-
RETARGETTING
static final int RETARGETTINGRETARGETTINGfilters examine a request and re-write the request so that it is dispatched to a different request URL. This is similar tomod_rewritein Apache, requests are examined and potentially re-targeted to different dispatchers depending on values in the request URL and/or request headers.- See Also:
-
DISPATCHING
static final int DISPATCHINGDISPATCHINGis the final phase, where a decision is made about which servlet will service the request- See Also:
-