Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

Magnolia uses the Java filter concept. A filter captures and processes a request before it reaches a servlet. Filters provide universal functions such as format the data sent back to the client.

DiagramArchitectural concept

Request processing and filter chain
The basic idea behind the filter chain is that the filters will be executed one by one until a filter decides that it can fulfill the request. See Request processing and filters.

Integration
Not all requests to the Magnolia filter chain come from users, or even from Magnolia. Independent servlets can also forward requests to the chain. Below are two examples of how to deal with a request, whether it comes from a client or an independent servlet

Integration: Responding to a request
An independent servlet or filter (grey box) outside Magnolia forwards a request to the Magnolia chain. Another servlet within Magnolia (red box) responds to the incoming request:

  1. Request arrives to Magnolia filter chain
  2. Request maps to a servlet
  3. Servlet handles the response

Integration: Forwarding a request
Alternatively, a servlet within Magnolia (blue box) can forward the request to another page:

  1. Request arrives to Magnolia filter chain
  2. Request maps to a servlet
  3. Servlet forwards request to another page
  4. Filter chain is re-executed
  5. Page is rendered

 

 

  • No labels