Refactor Shiro's Filters to favor composition over inheritance where possible.
------------------------------------------------------------------------------
Key: SHIRO-224
URL: https://issues.apache.org/jira/browse/SHIRO-224
Project: Shiro
Issue Type: Improvement
Components: Web
Reporter: Les Hazlewood
Fix For: 2.0.0
Scheduling to 2.0 initially as this might be disruptive.
Currently, to receive the benefits of the NameableFilter, OncePerRequestFilter,
PathMatchingFilter, etc, a user must subclass one of these classes. It would
be better to have a proxy of sorts that performs these functions for any filter
and wraps the 'real' target filter. This way, users' filter implementations do
not need to be tightly coupled to Shiro's API. This will also enable these
features for already existing filters so they don't need to be refactored to
subclass a Shiro class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
