[SLING-1213] Filters to support servlet-API-level scope configuration

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Engine 2.2.0
• Component/s: Engine
• Assignee: Felix Meschberger
• Reporter: Mike Pfaff
• Created: 01/Dec/09 15:29
• Updated: 02/May/13 02:29
• Resolved: 07/Sep/10 08:51

Description

Currently the filter.scope supports either

• component (comparable to <dispatcher>INCLUDE,FORWARD,ERROR</dispatcher> of the servlet API)
  or
• request (comparable to <dispatcher>REQUEST</dispatcher> of the servlet API)

In certain cases one wants to have finer control over the filter scopes, e.g. have a filter that would do <dispatcher>REQUEST,FORWARD</dispatcher>, so that the filter is applied first for the request and then again when you do a requestDispatcher.forward().

Therefore i suggest that the filter.scope should be enhanced as follows:

• Make filter.scope a multi-value property
• Add filter scopes: include, forward and error
• The existing filter scope "component"(quasi an alias for "include,forward,error") should for backward-compatibility not change.
• Add filter chains for the new filter scopes (don't know if this is needed internally?)

Issue Links

• is depended upon by: SLING-1140 Rewriter Filter not called when error is handled