abstract class AbstractTraceInterceptor : MethodInterceptor, Serializable
Base By default, log messages are written to the log for the interceptor class, not the class which is being intercepted. Setting the Subclasses must implement the |
|
abstract class AsyncExecutionAspectSupport : BeanFactoryAware
Base class for asynchronous method execution aspects, such as Provides support for executor qualification on a method-by-method basis. |
|
open class AsyncExecutionInterceptor : AsyncExecutionAspectSupport, MethodInterceptor, Ordered
AOP Alliance In terms of target method signatures, any parameter types are supported. However, the return type is constrained to either When the return type is As of Spring 3.1.2 the |
|
open class ConcurrencyThrottleInterceptor : ConcurrencyThrottleSupport, MethodInterceptor, Serializable
Interceptor that throttles concurrent access, blocking invocations if a specified concurrency limit is reached. Can be applied to methods of local services that involve heavy use of system resources, in a scenario where it is more efficient to throttle concurrency for a specific service rather than restricting the entire thread pool (e.g. the web container's thread pool). The default concurrency limit of this interceptor is 1. Specify the "concurrencyLimit" bean property to change this value. |
|
open class CustomizableTraceInterceptor : AbstractTraceInterceptor
Trace messages are written on method entry, and if the method invocation succeeds on method exit. If an invocation results in an exception, then an exception message is written. The contents of these trace messages is fully customizable and special placeholders are available to allow you to include runtime information in your log messages. The placeholders available are:
There are restrictions on which placeholders can be used in which messages: see the individual message properties for details on the valid placeholders. |
|
open class DebugInterceptor : SimpleTraceInterceptor
AOP Alliance Logs full invocation details on method entry and method exit, including invocation arguments and invocation count. This is only intended for debugging purposes; use |
|
abstract class ExposeBeanNameAdvisors
Convenient methods for creating advisors that may be used when autoproxying beans created with the Spring IoC container, binding the bean name to the current invocation. May support a Typically used in Spring auto-proxying, where the bean name is known at proxy creation time. |
|
open class ExposeInvocationInterceptor : MethodInterceptor, PriorityOrdered, Serializable
Interceptor that exposes the current org.aopalliance.intercept.MethodInvocation as a thread-local object. We occasionally need to do this; for example, when a pointcut (e.g. an AspectJ expression pointcut) needs to know the full invocation context. Don't use this interceptor unless this is really necessary. Target objects should not normally know about Spring AOP, as this creates a dependency on Spring API. Target objects should be plain POJOs as far as possible. If used, this interceptor will normally be the first in the interceptor chain. |
|
open class JamonPerformanceMonitorInterceptor : AbstractMonitoringInterceptor
Performance monitor interceptor that uses JAMon library to perform the performance measurement on the intercepted method and output the stats. In addition, it tracks/counts exceptions thrown by the intercepted method. The stack traces can be viewed in the JAMon web application. This code is inspired by Thierry Templier's blog. |
|
open class PerformanceMonitorInterceptor : AbstractMonitoringInterceptor
Simple AOP Alliance Uses a |
|
open class SimpleAsyncUncaughtExceptionHandler : AsyncUncaughtExceptionHandler
A default AsyncUncaughtExceptionHandler that simply logs the exception. |