Hi,
I came across an
interesting problem while trying to implement a particular security use case.
The use case is pretty simple - I need to secure the after-invocation of a
method, but not its invocation.
Since there is no
way to tell the MethodSecurityInterceptor to intercept just the
Vikas Sasidharan wrote:
I am not so enthusiastic about setting the flag to true. Could anybody
suggest some other possible alternatives? My last option is to have a
custom MethodSecurityInterceptor that enables separation of
before-invocation and after-invocation interception.
The problem is
