org.springframework.aop.framework

## 类 AopContext

- java.lang.Object
- - org.springframework.aop.framework.AopContext

-     public abstract class AopContext
      extends Object

  Class containing static methods used to obtain information about the current AOP invocation.

  The `currentProxy()` method is usable if the AOP framework is configured to expose the current proxy (not the default). It returns the AOP proxy in use. Target objects or advice can use this to make advised calls, in the same way as `getEJBObject()` can be used in EJBs. They can also use it to find advice configuration.

  Spring's AOP framework does not expose proxies by default, as there is a performance cost in doing so.

  The functionality in this class might be used by a target object that needed access to resources on the invocation. However, this approach should not be used when there is a reasonable alternative, as it makes application code dependent on usage under AOP and the Spring AOP framework in particular.

  从以下版本开始:
    13.03.2003
  作者:
    Rod Johnson, Juergen Hoeller

- - ### 构造器概要

    构造器
    构造器和说明
    `AopContext()`

  - ### 方法概要

    所有方法 静态方法 具体方法
    限定符和类型 | 方法和说明
    --- | ---
    `static Object` | `currentProxy()` Try to return the current AOP proxy.

    - ### 从类继承的方法 java.lang.Object

      `clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait`

- - ### 构造器详细资料

    - #### AopContext

          public AopContext()

  - ### 方法详细资料

    - #### currentProxy

          public static Object currentProxy()
                                     throws IllegalStateException

      Try to return the current AOP proxy. This method is usable only if the calling method has been invoked via AOP, and the AOP framework has been set to expose proxies. Otherwise, this method will throw an IllegalStateException.
      返回:
        Object the current AOP proxy (never returns `null`)
      抛出:
        `IllegalStateException` - if the proxy cannot be found, because the method was invoked outside an AOP invocation context, or because the AOP framework has not been configured to expose the proxy