Implementing objects can create AOP Alliance Interceptors from custom advice types, enabling these advice types to be used in the Spring AOP framework, which uses interception under the covers.
There is no need for most Spring users to implement this interface; do so only if you need to introduce more Advisor or Advice types to Spring.
| Modifier and Type | Method and Description |
|---|---|
| public MethodInterceptor | Returns: an AOP Alliance interceptor for this Advisor. There's no need to cache instances for efficiency, as the AOP framework caches advice chains.the Advisor. The supportsAdvice() method must have
returned true on this object advisor)Return an AOP Alliance MethodInterceptor exposing the behavior of the given advice to an interception-based AOP framework. |
| public boolean | Returns: whether this adapter understands the given advice objectan Advice such as a BeforeAdvice advice)Does this adapter understand this advice object? |
| getInterceptor | back to summary |
|---|---|
| public MethodInterceptor getInterceptor(Advisor advisor) Return an AOP Alliance MethodInterceptor exposing the behavior of the given advice to an interception-based AOP framework. Don't worry about any Pointcut contained in the Advisor; the AOP framework will take care of checking the pointcut.
| |
| supportsAdvice | back to summary |
|---|---|
| public boolean supportsAdvice(Advice advice) Does this adapter understand this advice object? Is it valid to
invoke the
| |