[PLUTO-539] New FilterManagerService implementation

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 11/Mar/09 15:25
• Updated: 11/Mar/09 16:07
• Resolved: 11/Mar/09 16:07

Description

Below copied (in part) from email discussion on the Pluto dev list, see also: http://www.nabble.com/More-required-Pluto-2.0-SPI-and-implementation-refactoring-issues-td21973310.html

• • • FilterManager implementation and usage
      The current implementation and usage of the FilterManager is very inefficient: a new FilterManagerImpl and FilterChainImpl is created on the
      fly for each container invocation, while the behavior and context of a PortletFilter really is deployment descriptor based.
      This implementation needs to be refactoring to a much more performant solution.

=====
I've added a new (required) FilterManagerService which will allow to cache a FilterChain per portlet application per FilterManager