Examples of FilterChain

• com.alibaba.druid.filter.FilterChain
  @author wenshao
• com.ettrema.mail.FilterChain
  Passes the request and response along a series of filters By default the MailServer loads a single filter which executes the appropriate handler for the http method Additional filters can be added using HttpManager.addFilter
• com.linkedin.r2.filter.FilterChain
  A chain of {@link Filter}s that get a chance to process or modify the request, wire attributes, and local attributes.

  Immutability

  Filter chains are immutable. Adding a new filter does not change the filter chain but instead produces a copy of the filter chain with the new filter inserted.

  Filter Order

  Requests are processed starting from the beginning of the chain and move towards the end of the filter chain. Responses are processed from the end of the filter chain and move back towards the beginning of the filter chain.

  If a request filter throws an exception, calls {@code nextFilter.onResponse(...)}, or calls {@code nextFilter.onError(..)} then that filter will have the appropriate responsemethod invoked (onResponse or onError). The response will flow back towards the beginning of the filter chain. Filters later in the chain will not get a change to process the request or the response.

  Filter Priority

  It is possible to implement a generic message filter and a message filter specific to a request type (RPC or REST). In general, this should be avoided. If a filter implements both types of interfaces then the more specific one is invoked and the less specific one is ignored.

  Wire Attributes

  Wire attributes provide a mechanism for sending request or response metadata to the remote endpoint. As an example, this facility can be used to send a unique request identifier from a client to a server.

  Local Attributes

  Filters must be stateless, so local attributes provide a mechanism for saving some state during the request which can be used during response processing. As an example, this facility can be used to store the time at which a request began so that total request latency can be logged when the response is received.

  @author Chris Pettitt
• com.qq.weixin.sdk.message.filter.FilterChain
  message filter chain @author hujiawei
• com.sun.hotspot.igv.filter.FilterChain
  @author Thomas Wuerthinger
• javax.servlet.FilterChain
  Interface def for chains of filters before invoking the resource. @author Rick Knowles
• mireka.filter.FilterChain
• net.matuschek.spider.docfilter.FilterChain
  This object defines a chain of DocumentFilters @author Daniel Matuschek @version $Revision: 1.1 $
• org.apache.abdera.protocol.server.FilterChain
• org.apache.tools.ant.types.FilterChain
  FilterChain may contain a chained set of filter readers.
• org.glassfish.grizzly.filterchain.FilterChain

  This class implement the "Chain of Responsibility" pattern (for more info, take a look at the classic "Gang of Four" design patterns book). Towards that end, the Chain API models a computation as a series of "protocol filter" that can be combined into a "protocol chain".

  The API for Filter consists of a two set of methods (handleXXX() and postXXX) which is passed a "protocol context" parameter containing the dynamic state of the computation, and whose return value is a {@link NextAction} that instructs FilterChain, how it shouldcontinue processing. The owning ProtocolChain must call the postXXX() method of each Filter in a FilterChain in reverse order of the invocation of their handleXXX() methods.

  The following picture describe how it Filter(s)

   ----------------------------------------------------------------------------- - Filter1.handleXXX() --> Filter2.handleXXX()                    |          - -                                                                |          - -                                                                |          - -                                                                |          - - Filter1.postXXX() <-- Filter2.postXXX()                        |          - ----------------------------------------------------------------------------- 

  The "context" abstraction is designed to isolate Filter implementations from the environment in which they are run (such as a Filter that can be used in either IIOP or HTTP parsing, without being tied directly to the API contracts of either of these environments). For Filter that need to allocate resources prior to delegation, and then release them upon return (even if a delegated-to Filter throws an exception), the "postXXX" method can be used for cleanup.

  @see Filter @see Codec @author Jeanfrancois Arcand @author Alexey Stashok
• org.openengsb.core.common.remote.FilterChain
  represents a chain of filters. This class basically represents just a FilterAction and can be used as final action of another FilterChain.
• org.sonatype.nexus.security.FilterChain
  A Shiro filter chain (mapping between a path pattern and a filter expression). @since 2.5

Examples of org.sonatype.nexus.security.FilterChain