Shiro
  1. Shiro
  2. SHIRO-224

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

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major 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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Les Hazlewood
          • Votes:
            4 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development