Uploaded image for project: 'Shiro'
  1. Shiro
  2. SHIRO-224

Refactor Shiro's Filters to favor composition over inheritance where possible.

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: Web
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              lhazlewood Les Hazlewood
            • Votes:
              5 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: