Spring Security
  1. Spring Security
  2. SEC-1216

Remove use of <custom-after-invocation-provider>

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.5, 3.0.0 M1
    • Fix Version/s: 3.0.0 M2
    • Component/s: Namespace
    • Labels:
      None

      Description

      For consistency, since we have now removed the decoration approach for both filters and authentication providers, it makes sense to do the same for AfterInvocationProvider instances. This will also remove the need for post processing of the MethodSecurityInterceptor created by the <global-method-security> element.

        Activity

        Hide
        Luke Taylor added a comment -

        This has now been done. AfterInvocationProviders should be added using <after-invocation-provider ref="someBean"> within the <global-method-security> element.

        Show
        Luke Taylor added a comment - This has now been done. AfterInvocationProviders should be added using <after-invocation-provider ref="someBean"> within the <global-method-security> element.

          People

          • Assignee:
            Luke Taylor
            Reporter:
            Luke Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: